home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
BBS Toolkit
/
BBS Toolkit.iso
/
programs
/
dci300d.zip
/
DCI300.DOC
next >
Wrap
Text File
|
1991-08-26
|
537KB
|
14,942 lines
DCI BBS Software
Version 3.00
August 26, 1991
Copyright 1989-1991
All Rights Reserved
Nordevald Software
P.O. Box 280138
Tampa, Florida 33682
data: (813)961-0788
TABLE of CONTENTS
DESIGN . . . . . . . . . . . . . . . . . . . . . . 1
SYSTEM REQUIREMENTS . . . . . . . . . . . . . . . . 1
FEATURES . . . . . . . . . . . . . . . . . . . . . 2
New in Version 3.00 . . . . . . . . . . . . . 2
SysOp Features . . . . . . . . . . . . . . . . 4
User Features . . . . . . . . . . . . . . . . 5
DCI EVALUATION VERSION . . . . . . . . . . . . . . 6
Nordevald Software Distribution Sites . . . . 7
UPGRADING TO THE REGISTERED VERSION . . . . . . . . 8
INSTALLING DCI . . . . . . . . . . . . . . . . . . 9
CONFIG.SYS . . . . . . . . . . . . . . . . . . 9
Directories . . . . . . . . . . . . . . . . . 9
Running DCI from a BATCH file . . . . . . . . 10
Command Line Switches . . . . . . . . . . . . 11
Running DCI . . . . . . . . . . . . . . . . . 12
THE WAITING SCREEN . . . . . . . . . . . . . . . . 14
LOGGING ON . . . . . . . . . . . . . . . . . . . . 16
GREETING . . . . . . . . . . . . . . . . . . . . . 17
MAIN MENU . . . . . . . . . . . . . . . . . . . . . 18
FILE MENU . . . . . . . . . . . . . . . . . . . . . 19
LOGOFF . . . . . . . . . . . . . . . . . . . . . . 20
MAIN/FILE: MISCELLANEOUS COMMANDS . . . . . . . . . 21
Help . . . . . . . . . . . . . . . . . . . . . 21
Xpert Toggle . . . . . . . . . . . . . . . . . 21
Information and Door Sections . . . . . . . . 21
Display Control . . . . . . . . . . . . . . . 21
MAIN: MESSAGE POSTING COMMANDS . . . . . . . . . . 22
Add a Message . . . . . . . . . . . . . . . . 22
Delete Message(s) . . . . . . . . . . . . . . 23
Feedback . . . . . . . . . . . . . . . . . . . 23
MAIN: MESSAGE READ COMMANDS . . . . . . . . . . . . 25
Message Headers . . . . . . . . . . . . . . . 25
Message Pointers . . . . . . . . . . . . . . . 25
Message Threading . . . . . . . . . . . . . . 26
Message # Prompt . . . . . . . . . . . . . . . 27
My Messages . . . . . . . . . . . . . . . . . 27
New Messages . . . . . . . . . . . . . . . . . 28
Read Messages . . . . . . . . . . . . . . . . 28
Message Read Prompt . . . . . . . . . . . . . 28
Message Scan . . . . . . . . . . . . . . . . . 30
i
Brief Scan . . . . . . . . . . . . . . . . . . 31
Scan Prompt . . . . . . . . . . . . . . . . . 31
MAIN: MISCELLANEOUS COMMANDS . . . . . . . . . . . 32
Base Description . . . . . . . . . . . . . . . 32
List Users . . . . . . . . . . . . . . . . . . 32
Operator Chat . . . . . . . . . . . . . . . . 32
Time . . . . . . . . . . . . . . . . . . . . . 33
MAIN: NAVIGATION COMMANDS . . . . . . . . . . . . . 34
Base List . . . . . . . . . . . . . . . . . . 34
Jump to Base . . . . . . . . . . . . . . . . . 34
Where are My Messages . . . . . . . . . . . . 35
Zip to New Messages . . . . . . . . . . . . . 35
<ENTER> or <+> (Move to Next Base) . . . . . . 35
<-> (Move to Previous Base) . . . . . . . . . 35
FILE: PROMPTS . . . . . . . . . . . . . . . . . . . 36
Directory [#] Prompts . . . . . . . . . . . . 36
Filename Prompts . . . . . . . . . . . . . . . 36
File Prompt . . . . . . . . . . . . . . . . . 36
FILE: FIND FILES . . . . . . . . . . . . . . . . . 37
List Directories . . . . . . . . . . . . . . . 37
New Files List . . . . . . . . . . . . . . . . 37
Search Files . . . . . . . . . . . . . . . . . 37
View File . . . . . . . . . . . . . . . . . . 38
FILE: TRANSFERS . . . . . . . . . . . . . . . . . . 39
Transfer Prompt . . . . . . . . . . . . . . . 39
Download . . . . . . . . . . . . . . . . . . . 39
Private Download . . . . . . . . . . . . . . . 40
Transfer Protocol . . . . . . . . . . . . . . 40
Upload . . . . . . . . . . . . . . . . . . . . 40
Designated Recipient Transfers . . . . . . . . 41
FILE: MISCELLANEOUS COMMANDS . . . . . . . . . . . 43
Exit . . . . . . . . . . . . . . . . . . . . . 43
Kopy . . . . . . . . . . . . . . . . . . . . . 43
Remove File . . . . . . . . . . . . . . . . . 43
Your Stats . . . . . . . . . . . . . . . . . . 43
CONFIGURATION SECTION . . . . . . . . . . . . . . . 45
Menu/Prompts . . . . . . . . . . . . . . . . . 45
Hot Keys . . . . . . . . . . . . . . . . . . . 45
Graphics . . . . . . . . . . . . . . . . . . . 45
ANSI Color . . . . . . . . . . . . . . . . . . 45
Editor Type . . . . . . . . . . . . . . . . . 46
Editor Screen . . . . . . . . . . . . . . . . 46
Password . . . . . . . . . . . . . . . . . . . 46
Computer Type . . . . . . . . . . . . . . . . 46
Screen Length . . . . . . . . . . . . . . . . 46
Screen Width . . . . . . . . . . . . . . . . . 46
Backspace Code . . . . . . . . . . . . . . . . 46
Msg Threading . . . . . . . . . . . . . . . . 47
Full Where Msg . . . . . . . . . . . . . . . . 47
Identities . . . . . . . . . . . . . . . . . . 47
ii
DOOR SECTIONS . . . . . . . . . . . . . . . . . . . 48
Modify and Add . . . . . . . . . . . . . . . . 48
Submenus . . . . . . . . . . . . . . . . . . . 51
List . . . . . . . . . . . . . . . . . . . . . 51
Purge . . . . . . . . . . . . . . . . . . . . 52
Rearrange . . . . . . . . . . . . . . . . . . 52
Sort . . . . . . . . . . . . . . . . . . . . . 52
Special Situations . . . . . . . . . . . . . . 52
Selecting Door Programs . . . . . . . . . . . 53
INFORMATION SECTIONS . . . . . . . . . . . . . . . 54
Modify . . . . . . . . . . . . . . . . . . . . 54
Purge . . . . . . . . . . . . . . . . . . . . 54
Submenu . . . . . . . . . . . . . . . . . . . 54
UTILITY SECTION . . . . . . . . . . . . . . . . . . 55
Adding Message Bases . . . . . . . . . . . . . 55
Modify Base . . . . . . . . . . . . . . . . . 61
Customize Base List Utility . . . . . . . . . 62
Ignore Base Utility . . . . . . . . . . . . . 62
Log to Disk Utility . . . . . . . . . . . . . 63
NonStop Read . . . . . . . . . . . . . . . . . 63
Recent Callers List . . . . . . . . . . . . . 63
Search User Utility . . . . . . . . . . . . . 63
MAIN SYSOP COMMANDS . . . . . . . . . . . . . . . . 64
SYSOP: BASE . . . . . . . . . . . . . . . . . . . . 65
Add Bases . . . . . . . . . . . . . . . . . . 65
List Bases . . . . . . . . . . . . . . . . . . 65
Modify Base . . . . . . . . . . . . . . . . . 66
Remove Base . . . . . . . . . . . . . . . . . 66
Board Info . . . . . . . . . . . . . . . . . . 67
Modem Setup . . . . . . . . . . . . . . . . . 70
System Setup . . . . . . . . . . . . . . . . . 72
Transfer Section . . . . . . . . . . . . . . . 74
New User . . . . . . . . . . . . . . . . . . . 76
Color/Screen . . . . . . . . . . . . . . . . . 78
Miscellaneous . . . . . . . . . . . . . . . . 79
SYSOP: FILES . . . . . . . . . . . . . . . . . . . 81
Color Test . . . . . . . . . . . . . . . . . . 81
Ansi View . . . . . . . . . . . . . . . . . . 81
View File . . . . . . . . . . . . . . . . . . 82
Edit File . . . . . . . . . . . . . . . . . . 82
Purge File . . . . . . . . . . . . . . . . . . 82
Search File . . . . . . . . . . . . . . . . . 82
SYSOP: MESSAGE . . . . . . . . . . . . . . . . . . 83
Header . . . . . . . . . . . . . . . . . . . . 83
Copy/Move Message . . . . . . . . . . . . . . 84
Delete Received Email . . . . . . . . . . . . 84
SYSOP: SYSTEM . . . . . . . . . . . . . . . . . . . 85
Bulletin Reset . . . . . . . . . . . . . . . . 85
Events . . . . . . . . . . . . . . . . . . . . 85
Rebuild Index . . . . . . . . . . . . . . . . 85
Date Set . . . . . . . . . . . . . . . . . . . 85
iii
Free Space . . . . . . . . . . . . . . . . . . 85
Time Set . . . . . . . . . . . . . . . . . . . 85
PrintScreen . . . . . . . . . . . . . . . . . 85
SYSOP: USER . . . . . . . . . . . . . . . . . . . . 86
Add User . . . . . . . . . . . . . . . . . . . 86
Delete User . . . . . . . . . . . . . . . . . 86
Modify User . . . . . . . . . . . . . . . . . 86
Search User File . . . . . . . . . . . . . . . 90
Group Modify . . . . . . . . . . . . . . . . . 91
FILE SYSOP COMMANDS . . . . . . . . . . . . . . . . 92
AddNew File . . . . . . . . . . . . . . . . . 92
DIRectory INFOrmation . . . . . . . . . . . . 92
FILE INFOrmation . . . . . . . . . . . . . . . 95
Text File List . . . . . . . . . . . . . . . . 98
Whole File List . . . . . . . . . . . . . . . 98
DOS Dir . . . . . . . . . . . . . . . . . . . 98
File Move . . . . . . . . . . . . . . . . . . 98
Mass Move . . . . . . . . . . . . . . . . . . 99
Purge Files . . . . . . . . . . . . . . . . . 99
Rearrange Directories . . . . . . . . . . . . 99
Sort Files . . . . . . . . . . . . . . . . . . 100
Virus and Integrity Checking . . . . . . . . . 100
DCI and DESQVIEW(tm) . . . . . . . . . . . . . . . 101
DISPLAY FILES . . . . . . . . . . . . . . . . . . . 102
Format . . . . . . . . . . . . . . . . . . . . 102
Special Codes . . . . . . . . . . . . . . . . 103
Required MNU Files . . . . . . . . . . . . . . 104
BULLETIN.MNU . . . . . . . . . . . . . . . . . 104
ETC.MNU . . . . . . . . . . . . . . . . . . . 104
FILEBULL.MNU . . . . . . . . . . . . . . . . . 105
HELP.MNU . . . . . . . . . . . . . . . . . . . 105
INFOFILE.MNU . . . . . . . . . . . . . . . . . 105
INFOMAIN.MNU . . . . . . . . . . . . . . . . . 105
LOGONOFF.MNU . . . . . . . . . . . . . . . . . 106
MENU.MNU . . . . . . . . . . . . . . . . . . . 106
REGISTER.MNU . . . . . . . . . . . . . . . . . 107
AltKey Files . . . . . . . . . . . . . . . . . 108
DROP TO DOS . . . . . . . . . . . . . . . . . . . . 109
EDITORS . . . . . . . . . . . . . . . . . . . . . . 110
ASCII Uploads . . . . . . . . . . . . . . . . 110
Color Codes . . . . . . . . . . . . . . . . . 110
Graphics Characters . . . . . . . . . . . . . 111
Mass Save . . . . . . . . . . . . . . . . . . 111
Include Files . . . . . . . . . . . . . . . . 112
Message Quoting . . . . . . . . . . . . . . . 112
ANSI Editor . . . . . . . . . . . . . . . . . 112
Non-ANSI Editor Commands . . . . . . . . . . . 117
EMS USAGE . . . . . . . . . . . . . . . . . . . . . 120
Fatal Error Messages . . . . . . . . . . . . . 120
Information Messages . . . . . . . . . . . . . 120
iv
EVENTS . . . . . . . . . . . . . . . . . . . . . . 121
Event Fields . . . . . . . . . . . . . . . . . 123
Event Commands . . . . . . . . . . . . . . . . 124
Internal Events . . . . . . . . . . . . . . . 125
Halt Events . . . . . . . . . . . . . . . . . 127
EXTERNAL DCI UTILITIES . . . . . . . . . . . . . . 128
DCI?SORT.EXE . . . . . . . . . . . . . . . . . 128
DCIEXPRT.EXE . . . . . . . . . . . . . . . . . 128
DCIFCNT.EXE . . . . . . . . . . . . . . . . . 129
DCIPATH.EXE . . . . . . . . . . . . . . . . . 130
DCIPURGE.EXE . . . . . . . . . . . . . . . . . 130
DCIUSER.EXE . . . . . . . . . . . . . . . . . 131
FATAL ERRORS . . . . . . . . . . . . . . . . . . . 132
File Errors . . . . . . . . . . . . . . . . . 132
Hardware Errors . . . . . . . . . . . . . . . 132
Software Errors . . . . . . . . . . . . . . . 132
Lock Ups . . . . . . . . . . . . . . . . . . . 132
The Most Frequent "Errors" . . . . . . . . . . 133
GROUP ACCOUNTS . . . . . . . . . . . . . . . . . . 134
INCLUDE FILES . . . . . . . . . . . . . . . . . . . 135
LOG FILES . . . . . . . . . . . . . . . . . . . . . 137
Activity Log . . . . . . . . . . . . . . . . . 137
Alert Log . . . . . . . . . . . . . . . . . . 141
Call Log . . . . . . . . . . . . . . . . . . . 141
Chat Log . . . . . . . . . . . . . . . . . . . 142
Download Log . . . . . . . . . . . . . . . . . 142
Failcall Log . . . . . . . . . . . . . . . . . 142
GoodArea Log . . . . . . . . . . . . . . . . . 143
LDPhone Log . . . . . . . . . . . . . . . . . 144
RegAlert Log . . . . . . . . . . . . . . . . . 144
TrashN Log . . . . . . . . . . . . . . . . . . 144
TrashP Log . . . . . . . . . . . . . . . . . . 145
User Log . . . . . . . . . . . . . . . . . . . 145
MAINTENANCE . . . . . . . . . . . . . . . . . . . . 146
Check Activity Log . . . . . . . . . . . . . . 146
Check Failcall Log . . . . . . . . . . . . . . 146
Purge Call Log . . . . . . . . . . . . . . . . 146
Back Up Board Files . . . . . . . . . . . . . 146
Deletion of Inactive Users . . . . . . . . . . 147
Deletion of Received E-Mail . . . . . . . . . 147
Deletion of Old Messages . . . . . . . . . . . 147
Moving Uploaded Files . . . . . . . . . . . . 148
File Directory Size . . . . . . . . . . . . . 148
Optimization . . . . . . . . . . . . . . . . . 148
PARAMETERS FOR DOORS/PROTOCOLS/EVENTS . . . . . . . 149
Parameter Codes . . . . . . . . . . . . . . . 150
DCI Exit . . . . . . . . . . . . . . . . . . . 150
Limiting Door Time . . . . . . . . . . . . . . 150
Updating the User Record . . . . . . . . . . . 151
User Name Format . . . . . . . . . . . . . . . 151
v
PROTOCOLS . . . . . . . . . . . . . . . . . . . . . 152
Choosing Protocols . . . . . . . . . . . . . . 152
Protocol Fields . . . . . . . . . . . . . . . 152
Protocol SysOp Commands . . . . . . . . . . . 154
RATIOS/PARTICIPATION . . . . . . . . . . . . . . . 156
Types of File Ratios . . . . . . . . . . . . . 156
Participation . . . . . . . . . . . . . . . . 156
Combined Ratio and Participation . . . . . . . 156
Free Downloads . . . . . . . . . . . . . . . . 157
SECURITY . . . . . . . . . . . . . . . . . . . . . 158
System Access . . . . . . . . . . . . . . . . 158
New User Registration and Access . . . . . . . 158
CoSysOps . . . . . . . . . . . . . . . . . . . 159
TempSysOp . . . . . . . . . . . . . . . . . . 159
Messages and Bases . . . . . . . . . . . . . . 159
Doors . . . . . . . . . . . . . . . . . . . . 160
SysOp Read . . . . . . . . . . . . . . . . . . 160
Include Files . . . . . . . . . . . . . . . . 160
File Section . . . . . . . . . . . . . . . . . 160
STATUS LINE . . . . . . . . . . . . . . . . . . . . 162
User Status Line I . . . . . . . . . . . . . . 162
User Status Line II . . . . . . . . . . . . . 162
User Status Line III . . . . . . . . . . . . . 162
User Status Line IV . . . . . . . . . . . . . 162
User Status Line V . . . . . . . . . . . . . . 162
New User Status Line I . . . . . . . . . . . . 163
New User Status Line II . . . . . . . . . . . 163
Command Line I . . . . . . . . . . . . . . . . 163
Command Line II . . . . . . . . . . . . . . . 163
Command Line III . . . . . . . . . . . . . . . 164
Command Line IV . . . . . . . . . . . . . . . 164
Command Line V . . . . . . . . . . . . . . . . 165
Unlisted Commands . . . . . . . . . . . . . . 165
TIME . . . . . . . . . . . . . . . . . . . . . . . 166
ACKNOWLEDGEMENTS . . . . . . . . . . . . . . . . . 167
APPENDIX A - MODEM SETTINGS . . . . . . . . . . . . A1
Practical Peripherals PM9600SA . . . . . . . . A2
USRobotics Courier HST 14.4 Modem . . . . . . A3
USRobotics Courier 2400 Modem . . . . . . . . A4
Viva Modem 24 . . . . . . . . . . . . . . . . A5
APPENDIX B - NORDEVALD SUPPORTING SOFTWARE . . . . B1
DCI Auto Access Door . . . . . . . . . . . . . B2
Nordevald Software Ballot Box . . . . . . . . B6
DCI Base Swap Utility . . . . . . . . . . . . B9
DCI B-Day Reminder . . . . . . . . . . . . . . B12
DCI Board Event Utility . . . . . . . . . . . B13
DCI BBS Call Log Utility . . . . . . . . . . . B16
DCI File Statistics Door . . . . . . . . . . . B19
DCI File Utility . . . . . . . . . . . . . . . B23
DCI MNU Swap Utility . . . . . . . . . . . . . B27
DCI Message Move Utility . . . . . . . . . . . B30
vi
DCI Potty Door . . . . . . . . . . . . . . . . B32
DCI Upgrade Door . . . . . . . . . . . . . . . B33
APPENDIX C - BIRD LAKE SUPPORTING SOFTWARE . . . . C1
BLUPurge, A DCI User Purge Utility . . . . . . C1
APPENDIX D - LONGBOW PUBLISHING . . . . . . . . . . D1
APPENDIX E - REGISTRATION AND ORDER FORMS . . . . . E1
DCI BBS Software . . . . . . . . . . . . . . . E1
Nordevald Software Order Form . . . . . . . . E4
Longbow Publishing Order Form . . . . . . . . E5
INDEX . . . . . . . . . . . . . . . . . . . . . . . E6
vii
DESIGN
DCI is a full-featured bulletin board system, providing
facilities for multiple bases, base formats, user
identities, file transfer options, and internal
callback verification. DCI was written in Borland
International's Turbo Pascal version 6.0 and Turbo
Assembler version 1.01.
DCI has been designed to be a versatile system, highly
secure and configurable to meet the needs of any
telecommunications environment, from that of the
serious hobbyist to the professional needs of the
business system.
DCI was designed so that the first time user, bbser or
SysOp, would find the environment inviting and easy to
use while the more experienced user would have numerous
features available to keep him satisfied.
DCI is easily and quickly installed and maintained.
Nordevald Software firmly believes that computers
should make life easier and more enjoyable. This
philosophy guides the development of DCI.
DCI contains all the features of a standard BBS program
and much, much more.
SYSTEM REQUIREMENTS
DCI requires an IBM PC/XT/AT or compatible computer
with a minimum of 384K, 1 floppy drive, and one hard
disk to run. A modem will extend the capabilities of
this software tremendously. DCI is fond of DOS
versions 3.0 through 5.0, will take advantage of EMS,
if available, and will run under DESQview(tm).
All of the features of the DCI BBS Software are
detailed in this manual. Any changes/updates made to
the software after the printing date will be included
in the text files NEW###.DOC and UPGR###.DOC.
1
FEATURES
New in Version 3.00
Message Section
- Number of message bases increased from 99 to 250
- Group Accounts
- Optional message received time and date stamps
- Toggle between Scan and Read on message prompt line
- Temporary Threading toggle at range prompt
- Counter for messages remaining when reading/scanning when
Message Threading is active
- Individual user Base List customization
- Verbose or brief Where Message listing
- Individual base description available from base prompt
- User alerts in editors when time is running out
- Letter Base Format
- Optional DOS path setting for each message base
- Optional local visibility of private bases
- Sysop configurable Mass Mail limits and security level
- Optional unvalidated posts
- Internal access to DCIPurge
File Section
- Three line descriptions on files
- Designated receiver private file transfers including
designated group accounts
- File section descriptions similar to Base List descriptions
- Option to save File Queue when aborting a download
- Download counts
- Option to check integrity of uploaded files
- Option to virus scan uploads
- CD ROM drive support
Door Sections
- Nested menus
- ANSI Only door setting
- Local Only and Remote Only settings
- Updated interface files
- Optional prompt for paramaters on SysOp doors
Miscellaneous
- Configurable menu and prompt displays
- ANSI supported input fields
- Additional commands for display files, including security
level
- Nested Information Section menus
- Easier configuration of Include files
2
Callback and Registration
- Optional dialing prefix and suffix
- Optional callback at every login (global or individual user)
- Optional long distance callback at every login
- Optional random callback of specified users
- Support for local calls to other area codes
- New user selection of ANSI editor screen color
- New user selection of transfer protocol
Sysop Features
- All new Installation program
- Note field available in user records
- User Note available on Status Line
- Chat Request Reason available on Status Line
- Modify user command from Read/Scan prompt
- Modify base command from Utility or SYS: BASE menu
- Selectable base number when adding a base
- Macros
- Def Files configurable to access from SYSOP: FILES menu with
a single key
- Activity Logging configuration
- Streamlined activity logging when using a front door program
- Option to always log chats
- Optional Logon password to completely restrict board access
- Option to disable F5 and F6 keys at local keyboard
- Modem rings setting to allow Caller ID on board line
- Null modem connections
- Option to take modem offhook when taking board down
- Option to rearrange order of event records
- Option to allow overtime usage when users are in a message
editor
- Options to allow access to Recent Call list and User Search
- Recent Call list available from Waiting Screen
- Activity Log listing available from Waiting Screen
- DCIPath utility to easily change board data file paths
3
SysOp Features
* Fully and easily configurable.
* DESQview(tm) Aware.
* Up to 250 Message Bases including open, private, and read
only.
* Fifteen message base formats including Standard, Debate,
Anonymous, StoryTelling, and Information.
* Supports Front Door programs for networking.
* Optional user handles.
* Optional file section.
* Unlimited file directories.
* Optional Main Doors and File Doors.
* Unlimited door programs.
* Internal support for all standard door interfaces.
* Support for 26 external protocols.
* Support for ARC, LZH, ZIP, and GIF external file viewers.
* Full control of individual user's access to message bases.
* Full control of users' access to doors & file directories.
* Ability to link message base with a door or file directory.
* Optional local and/or long-distance callback verification.
* Option to run private board.
* SysOp definable participation factor for download and
individual door access.
* SysOp definable file ratio.
* Twelve different local status lines.
* Global or individual user record modifications.
* Trash logs with name or phone number.
* Text files tied to user name or security level.
* Sliding-window events.
* 13 different event scheduling frequencies.
* Events can run external programs or 6 internal functions.
* Complete activity logging.
* 30 definable text colors + individual base colors.
* Unlimited bulletins with one-read bulletins at logon and file-
section entry.
* Definable upload categories.
* Mass file moving.
* Definable logon/logoff external programs.
* Definable external editor and file viewer.
* Full SysOp functions from remote.
* SysOp-Next function.
* Storm HotKey.
* Sound Silencing.
* Direct video and BIOS support.
* Optional daily time limits.
* Virtually maintenance free.
* Easily installed.
4
User Features
* Supports multiple global handles, up to 11 for each user
(SysOp's option).
* User-definable message bases (SysOp's option).
* Fifteen message-display formats (incl. anonymous).
* Optional message threading.
* Fully featured non-ANSI editor.
* Fully featured full-screen ANSI editor.
* Message text can be colorized.
* Message quoting.
* "Include" files for messages.
* Intuitive message addressing.
* Private messages blanked on local screen.
* Notification of messages addressed to user at logon.
* Displayed message status.
* Message scan capabilities with options.
* Forward, reverse, and personal message read.
* Message text formatted to user's screen width.
* Nonstop message reading.
* Logging to disk of new or personal messages.
* Message base list with descriptions.
* Mnemonic menu commands.
* Four prompt/menu levels.
* Abortable menu displays.
* Help displays at most prompts by entering ?.
* Ignore base option.
* Automatic verification.
* Support for non-standard terminals.
* Configurable color and graphics.
* Configurable hot keys.
* Wildcard support for file system.
* Private file transfers.
* On-line archive file viewing.
* Batch downloading.
* File tagging.
* Text search of file descriptions.
* 120-character file descriptions.
* Support for all standard door formats.
* Line noise filtering.
5
DCI EVALUATION VERSION
The evaluation copy of DCI is the "shareware" release of the
software. It is titled an evaluation copy because so many people
assume that "shareware" means "freeware". This is not the case.
Shareware is simply a means of distributing software which allows
people to try software before they purchase it.
Nordevald Software retains full copyright to the evaluation
version of DCI and to the documentation and supporting files.
The evaluation copy is provided so that SysOps may evaluate the
software to decide if it meets their needs. If so, registration
of the software is required. The evaluation period is not to
exceed 90 days.
The evaluation copy may be freely copied and distributed as long
as all files and documentation are included and not altered.
Distribution vendors may contact Nordevald Software in writing
for permission to distribute the software.
If you have obtained this copy of DCI from a vendor, you have
only paid for the distribution of the software; you have not
registered the software. Registration is required if you use the
software beyond a period of 90 days.
In addition to the numerous features offered in the evaluation
version, the registered version also offers:
Up to 250 message bases
Unlimited number of file directories
Unlimited number of users
Unlimited number of events
Unlimited number of doors in four door sections
Optional long distance callback verification
Message text and brief scans
Additional message base display formats
Support for front door programs to run BBS networking
software
Registered SysOps also have access to several more software
support bases and file directories on Nordevald Software BBS.
All other features of the software are available in this version.
The ten message bases allow you to evaluate several of the
fifteen message base formats. The three file directories include
a private directory, a public directory, and a directory for
include messages.
6
The evaluation program will remind the SysOp of the release date
when the software is run. This is to discourage the circulation
of old copies of the software.
Nordevald Software Distribution Sites:
The most recently updated version of DCI BBS Software can be
found online at the following locations:
Nordevald Software BBS* (813)961-0788 1200-9600 HST
(DCI Home Board) PcPursuitable FLTAM
Bird Lake BBS (813)265-3256 1200-2400
PcPursuitable FLTAM
Longbow BBS (813)961-3653 1200-9600 v.32
PcPursuitable FLTAM
OMNIBUS BBS (619)464-6271 1200-9600 v.32
PcPursuitable CASDI
BIX, BBS Conference listings
GEnie, BBS Roundtable listings
Or by writing to:
Nordevald Software
P.O. Box 280138
Tampa, Florida 33682
Please enclose $5.00 to cover postage and handling. We
usually send shipments out the next day but Snail Mail does
require a bit of patience.
* The DCI files may be downloaded on your first call and are in
the Nordevald Software directory in the file section. The
Auto Access door ( take * from the Main Menu ) allows
immediate access to several DCI support bases.
7
UPGRADING TO THE REGISTERED VERSION
To register DCI fill out the registration form in Appendix A of
this document and send it to Nordevald Software with the
licensing fee. Upon receipt of your order and payment, you will
receive the Registered Copy of DCI.
If you have been running the Evaluation Copy of DCI, you've
probably already customized many areas of your system. These do
not need to be changed. Several other features are available to
you now, specifically doors, events, long distance callback, and
additional file section directories. Review the documentation on
these sections.
NEW###.DOC contains any changes in the software.
UPGR###.DOC contains any changes in the data files. These
changes are very important. If this document was included with
your registered version of DCI, please review it carefully BEFORE
running the software and make any adjustments immediately. Also
read any README files immediately.
You should NOT run the Installation Program, simply replace your
DCI.EXE and DCI.OVR files with the new Registered copies. If you
have altered the MNU files do not replace them or your changes
will be lost.
8
INSTALLING DCI
To install DCI, follow the instructions below. If you attempt to
run DCI without first running the install program, you will get a
FATAL ERROR and DCI will not run.
Printing DCI.DOC is highly recommended. The documents have been
arranged to be bound in a notebook. The documents are ASCII
text, no specific printer codes are embedded, and should print
nicely on any printer, providing you with a handy reference guide
to the numerous features of the system. To print DCI.DOC from
the DOS prompt, enter TYPE DCI.DOC >PRN.
CONFIG.SYS
Check your CONFIG.SYS file to make sure it contains the following
entries:
files = 20
buffers = 20
device = ANSI.SYS
The files and buffers settings can be higher than 20, but they
should not be set at a lower value. The ANSI.SYS entry must
include the full pathname to ANSI.SYS if it is not in your root
directory.
Directories
DCI needs to have a main directory. It can be located anywhere
on your hard drive, but it is suggested that it be located
directly off the root directory on Drive C.
You will need the following files in order to run DCI:
DCI.EXE
DCI.OVR
DCIFSORT.EXE
DCIHSORT.EXE
DCIDSORT.EXE
DCIUSER.EXE
DCIPURGE.EXE
Create a directory named DCI (MD DCI) and copy all the DCI files
to it. From this directory, run DCI_INST, the DCI installation
program.
If your system is located in Canada, run DCI_INST by typing
DCI_INST /C. This will tell DCI to set up the system so that
users are prompted for province rather than state information.
9
The install program will create all the necessary data files and
subdirectories that DCI needs to run. The program will prompt
you for necessary information. Once it is complete, you can run
the DCI program. You can change any of the setup information by
using the SysOp Menu available by pressing "1" at the Main Menu.
(see SYSOP: BOARD).
The installation program will create the following directories
for the DCI files:
\UPLOADS Directory for transfer section open files.
\PRIV Directory for transfer section private files.
\MSG Directory for message base files.
\MNU Directory for DCI menus.
\DOORS Directory for external door programs.
\LOGS Directory for the DCI .LOG files.
Running DCI from a BATCH file
As a precaution against power outages, it is suggested that you
create a batch file and enter the name of the batch file in your
AUTOEXEC.BAT file. If you do have a power outage, when power is
restored the batch file will ensure that the board is put back
up.
Enclosed with the DCI program is a small program named ALARM.EXE.
This is used in a looping batch file so that you know when the
board is taken down and also to give you time to exit the board
and break the loop of the batch file (by typing Control-C as
ALARM is sounding) to return to the DOS prompt.
DCIBAT.BAT is included in your software package. If you have set
your Main DCI Directory to C:\DCI, you can use this batch file as
is. Otherwise, you will need to change the second line of the
batch file to reflect your Main DCI Directory.
Remember, to exit this batch file you will need to enter a
Control-C, or BREAK, after DCI exits.
To enter this batch file in your AUTOEXEC.BAT file, use EDLIN
(EDLIN AUTOEXEC.BAT) and insert a line after any SET, PROMPT, and
PATH commands and enter DCIBAT. You should also add the pathname
to the DCI directory to your PATH statement. Then save the file.
When AUTOEXEC.BAT executes, it will run DCIBAT.BAT. You will
have to reboot your machine to run AUTOEXEC.BAT again with the
new information.
10
Command Line Switches
DCI supports several command line switches. These are commands
you can enter when you run DCI. To view a help screen of these
commands, type DCI /? at the DOS prompt.
DCI will recognize the following command line switches, each of
which is explained in more detail below:
/COLOR or /C
/DELAY# or /D#
/MONO or /M
/NOCHECK or /NOC
/NOEMS or /NOE
/NOPRINT or /NOP
/ONLINE# or /O#
/SNOW or /S
/TIMER or /T
/VERIFY or /V
If you are using a monochrome monitor or if your system is
running in monochrome mode, DCI should correctly recognize this
and make adjustments so that all colors are displayed correctly
on your screen. You can force DCI to use either monochrome or
color display by adding a switch when you run the program:
DCI (DCI will autodetect monitor type)
DCI /M (force monochrome display)
DCI /C (force color display)
You may also enter these as DCI /MONO or DCI /COLOR if you wish.
If you have an older CGA monitor, you may experience problems
with "snow" on your screen. To increase the speed of screen
writes, DCI does not automatically perform snow checking. If you
would like snow checking, enter the /SNOW switch on the command
line:
DCI /SNOW or DCI /S
DCI automatically checks to see if it is running in a shell of
itself (via a Drop to DOS command). If you have problems with
DCI telling you that it is already loaded when it is not, run DCI
with the /NOCHECK switch:
DCI /NOCHECK or DCI /NOC
DCI automatically uses EMS memory if available. If you do not
want the program using this memory, use the /NOEMS switch:
DCI /NOEMS or DCI /NOE
DCI provides a short delay when telling the modem to answer the
phone. Some older modems need a slightly longer delay. You can
alter this by using the /DELAY switch followed by the length of
the delay in milliseconds. The delay can range from 1 to 10,000.
For instance:
11
DCI /DELAY100 (increase delay 100 milliseconds)
DCI /D100
Under normal circumstances, this delay should not exceed 2000.
Greater values indicate a problem in your modem configuration.
DCI maintains several data files that are necessary to the proper
functioning of the board. You can force DCI to verify these
files when it first executes. If DCI finds a problem, it will
rebuild the files. This does take a short time and hence is not
done automatically. By using the /V command line switch, you can
tell DCI to verify these files when it is first executed.
DCI /VERIFY or DCI /V
If you have any problems with "User not found" or "File not
found" or message bases that can't be selected, take the board
down and rerun it with the /V switch.
DCI also provides an option to disable the PrintScreen key so
that accidently pressing it will not activate the printer.
DCI /NOPRINT or DCI /NOP
In order to run a front end program to handle networking, you
must tell DCI to share control of the modem and comm port.
Running DCI with the /ONLINE<speed> switch accomplishes this
task.
DCI /ONLINE2400 (incoming call at 2400bps)
DCI /O2400
The front door program must be configured to pass the baud rate
<speed> of the caller along to DCI. This option is available in
registered versions of DCI only.
You can use more than one switch. The format is:
DCI /option1 /option2 /option3 /option4 /option5.
To disable any of these commands, you will have to exit DCI and
run it again without the command switch.
Running DCI
DCI must be run from the Main DCI Directory or it will not be
able to find the files it needs.
Store your original copy of the software on a floppy diskette in
a safe place.
When you run DCI, the program will read in some data and display
a message concerning EMS usage and then you will see the Waiting
Screen. This screen will blank after 30 seconds. Strike the
spacebar to turn it on and off.
12
Enter an L to logon the board. As the SysOp, your user number is
1. You can enter this at the Name prompt and then enter your
password and you're online.
Enter "1" from the main menu prompt and select C)onfig. This is
the System Configuration and contains the information you entered
during the Install program and the default values that the
Install program entered.
Select each item from the menu and make sure that all the
information is correct. At this point you should primarily be
concerned with the baud rates, the security level setting of the
file section and doors, and whether or not you wish to allow
access to new and/or long distance users.
You need to modify several of the MNU files to customize them for
your system. This is best done with a text editor. Do not use a
word processor. Eventually you will probably want to change most
of them, but for now it is only necessary to modify the
following:
INFO.MNU section one - add your system policy.
REGISTER.MNU section one - add your bbs name.
section four - add the terms of access.
LOGONOFF.MNU you may also wish to add logon and logoff
screens To this file.
Without any other changes, you may now allow users to enter your
system.
If you are not familiar with DCI, read through the documentation
at least once as you try the various commands. At this point,
you will probably want to pay close attention to Adding Bases and
Creating File Directories. You will also want to read over the
section on New User Registration.
Because DCI is file intensive, a disk cache, with cache size set
between 40 and 60K, will greatly improve the speed at which files
are accessed and the amount of disk reading and writing,
particularly on machines operating at less than 10 megahertz.
Disk cache programs will out perform DOS's buffers for this task.
Please consult the disk cache documentation for installation and
usage information.
13
THE WAITING SCREEN
The Waiting Screen displays just after you run DCI or a caller
logs off. The screen shows the valid keys to use while DCI is
waiting for calls. The screen will also show your registration
number and the current time. If the call log is not empty (which
it will be when you first run the program) the last caller's name
and brief information will be displayed at the top of the screen.
A tilde (~) before the user's name indicates a surreptitious
visit (invisible logon).
This screen will be shown for 30 seconds every time the program
recycles, after that time the screen will go blank to prevent
monitor burn-in. If the screen is blank, simply press the
spacebar and the screen will redisplay for another 30 seconds.
If any of the keys that toggle options on this screen are
pressed, the screen will also redisplay.
The Registration Box displays your registration number, name, and
the date that you registered the DCI Software.
The Event Box tells you when the next event is scheduled to
occur, or NONE if events are turned off. When you have events
defined, you can toggle them on and off from the waiting screen
by pressing the E key.
The Nordevald Software box reminds you that support for your
software is only a phone call or a postcard away. If you have
any questions at all, please contact us.
The Command Box offers you several options:
L Logon Locally
This is the key you use to log on the board from the local
keyboard.
R Recent Caller List
Display a listing of the Call Log.
W Where Messages
List the bases where the sysop has new messages.
E Toggle Events
Turn the event handler off and on.
P Toggle SysOp Page
Whether or not to alert the SysOp to a chat page.
Q Quit
Take the board down/return to DOS.
When you take the board down, you have the option of also taking
the modem offhook (so that any callers will get a busy signal).
To do this, DCI uses the modem's local init string. Do make sure
you test this to make sure it is working correctly and that the
modem goes back onhook again when the board is put back up. If
you have any doubts, press L for logon and then press <ENTER> 5
times to cycle the board.
14
Three commands are not shown. Pressing the F key will force the
Next Event to execute immediately. Entering Alt-J will allow you
to shell to DOS (provided you enter the system password
correctly) without taking the board down . To connect to DCI via
null modem, press N at the Waiting Screen and follow the prompts
(entering baud rate and comm port information).
15
LOGGING ON
In order to logon to your board from local mode, press L. You
will be prompted for name and password. This will write the
local initialization string to the modem, and you will be able to
access the board.
At logon, if the user does not enter the correct information
after five tries the board will then disconnect and recycle,
waiting for the next user to logon.
There are several ways to enter logon information:
Enter name (handle) and press <ENTER>. If the name is not
found, a message will display: "The name <whatever was
entered> is not on file. Please enter your Handle or logon as
NEW." If the name is found, the user will then be prompted for
PASSWORD. If this is not entered correctly, the system will
beep and begin the logon process again.
Enter user number and press <ENTER>. If the user number is
valid, the password prompt will appear.
Enter user name and password separated by a semicolon
(User Name;PASSWORD).
Enter user name, password, and color/graphics selection.
User Name;PASSWORD;N no graphics, no color.
User Name;PASSWORD;G graphics, no color.
User Name;PASSWORD;C graphics, color.
Specifying color and graphics in this way does not change the
user's record, it only changes the color and graphics settings
for this session. This option is of importance to people who
logon from multiple terminals with different color and graphics
capabilities.
16
GREETING
After the user has completed logging on, the system will then
display the appropriate greeting screen (see Display
Files/LOGONOFF.MNU).
If an Auto-Logon Program has been defined it will run at this
point.
The system then welcomes the user, tells him the current time and
date, the date of his last call, and how many times he has called
the system. If the Call Log is not empty, the previous caller's
system name and city are listed.
The system then tells the user if he has new messages waiting and
which bases they are in. The user can see this information again
from the Main Menu by selecting W)here Messages.
Any user who has an access level above 85 will be prompted with
"Visiting Surreptitiously?". This is to allow the user to log on
the system without being visibly written to the call log. The
SysOp will not see this prompt as the SysOp account is never
written to the call log. If the user's access level is 85 or
below, the call will automatically be recorded in the Call Log.
If this is the first call by a user who was added by the SysOp or
verified by Long Distance Callback, the user will then be shown
the Final Text of REGISTER.MNU. SysOp-added users will also be
prompted to verify their phone numbers and birth date.
The permanent Main Bulletin is now displayed and if the user has
not read the one-read-only Main Bulletin, it will also be
displayed.
If an event is scheduled which falls within the user's allotted
time, a message will display at this point telling the user how
much time he has until he must logoff so that the event can run
and reassuring him that his account will be credited.
Novice users will then be presented with the Main Menu and a base
prompt. Main and File Menus are not displayed automatically to
Expert users. If the user has new messages in E-Mail, he will be
at the E-Mail base, base one; otherwise, he will be at the second
base.
17
MAIN MENU
The Main Menu is the center of the system. You may design this
menu to suit the needs of your system. Include on it all of the
commands that are available to the average user. Keep in mind
that users in novice mode will be seeing this menu repeatedly.
Modest use of color changes will improve the speed at which it is
displayed.
The Main Menu always appears above a base prompt. The base
prompt includes the name and number of the current base, the
total number of messages in the base, how many are new (unread)
to the user, and a command line. The command line includes the
Main Command Options that are available to the user. If there
are new messages in the base addressed to the user, the message
"Message(s) to you here!" will be displayed.
The SysOp has ultimate control over what commands are available
to each user from this menu by modifying the Main Command Options
of each user and of new users. Following is a list of the
commands that DCI allows from this menu. They are grouped
according to the documentation section that covers them in
detail.
Logoff Commands: Miscellaneous Main & File
Goodbye Commands:
Help
Message Posting Commands: Xpert
Add a Message
Delete a Message Navigation Commands:
Base List
Message Reading Commands: Jump to Base
My messages Where Messages
New messages Zip to New
Read messages Next Base
Scan messages Previous Base
Miscellaneous Main Commands: Submenus:
List users Configuration
Operator chat Doors
Time File Menu
Base Description Information
Utility
Each of the submenus has a separate section in this
documentation.
18
FILE MENU
The File Menu is a submenu off the Main Menu. As with the Main
Menu, you may design the File Menu to suit the needs of your
system. Include on it all of the commands that are available to
the average user.
Only users who have a security level equal to or greater than the
File Access Level will be able to get into the file section. If
the user's security level drops below the File Access Level while
the user is in the file section, he will be returned to the Main
Menu.
The File Menu is displayed above the file command prompt. This
prompt lists the time the user has left followed by the File
Command Options available to the user. If a user has CoSysOp
access, the 1 command (for SysOp functions) is automatically
added to the File Command Options, though it is not stored in the
user's record.
When a user enters the File Section, the permanent bulletin from
FILEBULL.MNU is displayed. If the user has not read the
one-read-only File Bulletin, it will also be displayed. If the
user is in Novice mode, the menu will be displayed followed by
the file command line.
The SysOp has ultimate control over what commands are available
to each user from this menu by modifying the File Main Command
Options of each user and of new users. Following is a list of
the commands that DCI allows from this menu. They are grouped
according to the documentation section that covers them in
detail.
Find Files Commands: Miscellaneous Main & File
List Directories Commands:
New Files Help
Search Xpert
View File
Submenus:
Logoff Command: Doors
Goodbye Information
Miscellaneous File Commands: Transfer Commands:
Exit Download
Kopy Private Download
Remove File Transfer Protocol
Your Stats Upload
19
LOGOFF
The user may logoff the board (disconnect) by entering G for
Goodbye from either the Main or File Menu. The user will be
asked to confirm that he is ready to logoff. If the user enters N
(no) he will be returned to the menu. If the user enters R
(relogon), he will be returned to the logon prompt of the board.
This allows users who share terminals to log on under their
separate accounts without disconnecting.
If the user responds with Y (yes) or <ENTER>, he will have the
option of leaving feedback to the SysOp. If an Auto-Logoff
Program is defined, it will be executed at this point. The
appropriate section of LOGONOFF.MNU will be displayed and the
board will disconnect, recycle, and display the Waiting Screen.
The user can also select Autologoff when transferring a file.
After the file is transferred, the user will have approximately
10 seconds before being disconnected. He can press any key and be
returned to the system. If the user does not press a key, the
system will display "Logged off <board name> at <time>." and
disconnect. The Auto-Logoff program will not be run and no logoff
screens will be displayed.
If the user exceeds his time limit, the system will log him off
displaying a message of explanation and giving him the option of
leaving feedback. He will not have the opportunity of returning
to the menu or relogging on.
When a user drops carrier, rather than logging off properly with
the G)oodbye command, DCI simply recycles and waits for the next
caller. While dropping carrier may be considered bad BBS
manners, it does no harm to the system.
20
MAIN/FILE: MISCELLANEOUS COMMANDS
Help
The Help command (H from either menu) displays the appropriate
section of HELP.MNU. You may alter these files as necessary, but
make sure they contain explanations of all the commands you allow
the average user on each menu.
The user may pause or stop the display with the P and S or
spacebar keys respectively.
Xpert Toggle
This command toggles menu displays between Novice (menus
automatically displayed) and Expert (no menus displayed) mode.
It is available from both the Main and File Menus.
If a user is in Novice mode, entering a question mark at either
menu will display the appropriate HELP.MNU section. If a user is
in Expert mode, entering a question mark will display the menu.
The user may also set menu/prompt level from the C)onfiguration
Menu.
Information and Door Sections are also available from each menu.
Each is covered in a separate section in the documentation.
Display Control
Most displays, including menus, user lists, messages, file lists,
and display files, can be paused by pressing P. They can also be
aborted by pressing S or the spacebar.
Control-X and Control-C can be used to stop the display and will
not be interpreted by the message prompt as S)top.
The system will pause displays with *MORE* prompts depending on
the user's screen length setting. These prompts can be disabled
totally by setting screen length to 0. Although not visible,
*MORE* prompts do accept the following commands:
N, S, Q stop the display and return to the prompt.
(Mnemonics: N)o, S)top, Q)uit)
C turn NonStop Read on.
(Mnemonic: C)ontinuous)
? display the above options.
21
MAIN: MESSAGE POSTING COMMANDS
Add a Message
To post a message in the current base, enter A. Depending on the
message display format of the base, the system may prompt you to
enter Header information, such as who the message is addressed to
and the subject of the message.
Below is information on the standard prompts. Not all are used
in each message display format. You will only be prompted for
the information necessary.
Standard Prompts:
TO: Pressing <ENTER> will enter the message to ALL USERS.
Otherwise, the addressee's handle or part of his
handle must be entered. If only part is entered, the
system will search and display handles that match,
asking for confirmation. If you respond with an A
for Abort, you will be returned to the base prompt.
FROM: If you have adopted multiple personalities, the
system will prompt for which personality is posting
the message at the FROM prompt. Enter all or the
first part of the name, the handle number (0-10), or
press <ENTER> to use your system name.
SUBJECT: Enter the topic of the message. The subject can be
up to 30 characters long. In message bases with the
Standard, Gaming, or Information format, when
replying to a previous message, pressing <ENTER> will
retain the subject of the original message.
POSITION: (<P>ro, <C>on, <U>ndeclared) Enter P, C, or U to
declare your position on the subject being discussed.
When replying, you will also have the option of
changing the <S>ubject. This prompt appears in bases
using the Debate and Secret Ballot message formats.
RATING: (<1>-<5> Stars, <B>ig Boo, <U>nrated) Enter a
number, B, or U to indicate the rating you give the
subject. When replying, you will also have the
option of changing the <S>ubject. This prompt
appears in bases using the Five-Star and Secret
Rating message formats.
OPEN/PRIV: Enter an O or P to designate whether the message is
Open or Private. This prompt is only used in bases
using the Gaming Format. All messages posted in
E-Mail are automatically set to Private and all
messages posted in other bases are automatically set
to Open.
ACTION: Enter the action of the character. This prompt is
used in bases using the Action format. If you are
posting using the handle Simon, the action might be
"says."
22
You may then type in the text of your message (see EDITORS).
Both editors allow you to change From, Subject, Position, Rating,
and Action entries before you save the message. When you save
the message it is automatically posted in the base you are in.
Messages may also be added by R)eplying to a message. In this
case, you will not be prompted TO: as the message will be
addressed to the person who posted the original message.
If you have handles defined and are replying to a message that is
addressed to you, the system will prompt you at the FROM prompt
with the handle used in the original message. The default
response is Yes so that a person replying to messages in a thread
can simply hit <ENTER> twice to keep the same handle and subject
line as the original post.
Delete Message(s)
The Delete command, D, from the Main Menu, allows a user to
delete a message that is posted to him or posted by him provided
the message is not Protected or posted by the SysOp using his
system name.
If the user is the base creator, he may delete any message in the
base that is not protected or posted by the SysOp using his
system name.
Users with less than CoSysOp access will be prompted for the
number of the message to delete and then shown the message header
and asked to confirm the deletion before the message status is
changed to deleted.
The SysOp and CoSysOps will be prompted for the range of messages
to delete. There will be no prompts for confirmation.
A SysOp may delete an individual message at the prompt of the
message that he wishes to delete by pressing D. A user may
delete a message posted to or by him in this manner.
Deleted messages are not actually removed from the data files
until a Purge, their status is simply changed to Deleted and they
are not displayed. The status of Deleted Messages can be changed
by using the SYSOP: MSG: Header command.
Feedback
There are three different instances where users have the option
of leaving feedback, a message, to the SysOp.
When logging off the system, if a user elects to leave feedback
to the SysOp, the message will be saved in the E-Mail base with
the subject as "Feedback".
If a user requests chat and the chat call is not answered, he
will have the option of leaving feedback. If the fourth section
of ETC.MNU contains text, it will be displayed before the
23
feedback prompt. This feedback is saved to the E-Mail base with
the subject "Chat Request".
New users who do not complete Registration are also given the
option of leaving feedback. In this case, the message is saved
to the Failcall.Log (see NEW USER REGISTRATION/LOG FILES).
24
MAIN: MESSAGE READ COMMANDS
DCI provides several commands for users to read and scan messages
depending on which messages they wish to see and if they want to
reset their message pointer in the current base.
Depending on the command chosen and the status of messages in the
base, sometimes the system has to search for messages that fit
the Read/Scan criteria that the user has entered. If this is the
case, an indication that the system is working, a "Looking"
message, appears on the screen. This process can be aborted by
the user by pressing any key.
Message Headers
The message format of the base determines what information is
displayed in a message header. On messages with full headers,
either "Open Message" or "Private Message" is displayed followed
by a letter indicating the Message Status. R means the message
has been Received (messages to ALL USERS are automatically marked
as Received), N indicates Not Received, and P indicates
Protected. The SysOp, Cosysop, and Base Creator may also see U
to indicate Unvalidated. The Sysop, if SysRead is on, will see
Deleted messages with a Message Status of D.
When Message Threading is on, a number will appear to the right
of "Message # <n> of <total>" in the message header. This number
indicates the number of messages remaining in the current message
read.
In bases with no TO information, when a user reads or scans a
message posted to him an asterisk will appear under the dividing
line.
In bases using the Narrative, Action, and Dated Dialogue formats,
an asterisk next to the header information will indicate that the
message is a reply to a message posted by the current user.
Message Pointers
The system keeps track of the messages that a user has read in
his user file. Only Reading Messages in a forward direction or
reading New Messages will change the user's pointer. My Message
Read in E-Mail will also update a user's pointers.
This gives the user several options. A SysOp can scan E-Mail,
read, and reply to pressing messages and then later read through
all his E-Mail. A user may only have time to read messages
posted to him but wants to read all new at a later date. He can
select My Message Read.
The user may also include a P at the Message # Prompt when
reading forward to tell the system not to update his pointers.
25
Message Threading
DCI gives the user the option of reading/scanning messages either
sequentially or by message threads. Users may permanently set
threading status from the Configuration menu or temporarily
change it from the Message Read Prompt. Any changes in threading
from the message read prompt will apply to the current action
(read/scan) in the current base only.
DCI maintains message threads in all base formats. Each time a
user posts a message using the A)dd message command from the base
prompt, a new message thread is begun. When a user enters a
message by R)eplying to another message, that message thread is
increased. Message threads may branch in numerous directions
such as when there is more than one reply to a message.
Most users find that message threading makes it much easier to
follow discussions within a base. However, navigating through
threads can often be confusing as can understanding how users'
message pointers are updated. The following diagram shows how
DCI threading works.
Msg #1 Msg #10 Msg #12 Msg #16
| | | |
2 5 14 15
__|_ | |
| | 7 17
3 4 |
| | 8
9 6
|
11
With threading on, the messages would be read in this order:
1, 2, 3, 9, 11, 4, 6, 5, 7, 8, 10, 14, 12, 15, 17, 16
Q)uitting a thread goes to the next branch or next major thread.
For instance, if the user Q)uits at msg #9, the next message will
be #4; Q)uitting at #4 would go to #5; and Q)uitting at #5 would
go to #10.
The P)revious command will go back to the previously viewed
message. For instance, selecting P)revious at message #2 will go
to message #1; P)revious from message #4 will go to message #11.
Updating the user's message pointers is a bit complicated.
S)topping at #3, will set the pointer to 4 (the next unread
message). However, if S)topping at #9 with threading on, the
pointer will still be set to #4 (otherwise messages #4-8 would be
missed).
26
To avoid confusion, users should be encouraged to read all
messages with either Threading ON or Threading OFF.
Message # Prompt
All of the read and scan commands, except New, prompt the user
for a range of message numbers. The following options are
available at the "message #" prompt:
Enter a number = Forward from that message number to the last
message in the base (e.g. 100).
Enter a number followed by a plus sign = Forward from that
message number to the last message in the base (e.g. 100+).
Enter a number followed by a minus sign = Reverse from that
message number to the first message in the base (e.g. 100-).
Enter a number followed by a period = Display just message number
# and return to the base prompt (e.g. 100.).
Enter two numbers separated by a semicolon = From first number to
second, either forward or reverse (e.g. 100;110 or 110;100).
Enter two numbers separated by a space = From first number to
second, either forward or reverse (e.g. 100 110 or 110 100).
Enter N = From first new message (e.g. N 110, N-).
Enter L = From last message (e.g. L- )
Enter ? = display input options
NS can be added to any of the above entries to invoke Nonstop
display. NonStop will only be active until the user returns to
the base prompt. For instance, N NS, will read all new messages
with NonStop active (e.g. 100- NS, 100;110 NS, 100 NS).
P can also be added to any of the above entries to prevent
message pointers from being updated or messages being marked as
Received during the current read. (e.g. N P, 100;110 P).
Adding a T will toggle the message threading setting temporarily
(until it is changed from a message prompt or the user returns to
the base prompt). (e.g. 100;110 T )
My Messages
This command, M, will display all messages posted by and to the
user within the range of messages indicated at the message range
prompt. In bases other than E-Mail, this command does not reset
the user's message pointer in the base.
27
New Messages
The New Message command, N, will display all new messages in the
current base. This is a shortcut way of Reading Messages from #N.
All open messages and any private messages addressed either to or
from the user will be displayed.
If there are no new messages in the base, the last message (if it
has not been deleted) will be displayed. This allows users to
quickly check out the current topic in a base that hasn't
received any new posts since they last read messages in the base.
Read Messages
This command, R, will display all open and any private messages
posted to or by the user within the range specified by the user.
If the direction is forward, the user's message pointer in the
base will be updated.
Message Read Prompt
After a message is displayed, the Message Prompt appears on the
screen. This prompt has several visible options (available to
all users) and several invisible ones (available primarily to the
SysOp and CoSysOp). This prompt is displayed when reading
messages either by using one of the Main Menu message read
commands or when electing to read a message during a message
scan. This prompt does not appear if the user has NonStop
activated.
Visible Options:
[N]ext message
Enter N or <ENTER> to display the next message.
R)eply
Post a message in reply to this message. If a message is Open
and more than 30 days old, this option will not appear, but can
still be used. This is to discourage users from replying to old
messages, a practice that most regular users find annoying.
If a user has handles defined and is replying to a message that
is addressed to him, the system will prompt the user at the FROM
prompt with the handle used in the original message. The default
response is Yes so that a person replying to messages in a thread
can simply press <ENTER> twice to keep the same handle and
subject line as the original post.
O)riginal
If the message is a reply to another message (RE: ## will appear
in the message header of most message formats), select this
option to read the original message.
28
P)revious
Select this option to read the previous message, if available.
With Threading off, this command will take the user to the
previous message until either the first or last message is
reached or the user selects N)ext or S)top. The N)ext command
will simply reverse the direction of the read/scan and take the
user back through the messages again. When Threading is on, the
user may go back to the end of previously read threads ten times.
Once the user chooses to go to the N)ext message after a
P)revious read, he will be returned to the message at which he
first selected P)revious (this is the same way O)riginal works)
rather than scrolling back through all the previously read
messages.
A)gain
Show this message again.
T)hread OFF (visible if message threading is on)
Temporarily turn threading off; applies to current read/scan
only.
T)hread ON (visible if message threading is off)
Temporarily turn threading on; applies to current read/scan only.
Q)uit Thread (visible if message threading is on)
Stop reading the current thread. Any messages in the thread are
skipped. If the user continues on to read the entire base, these
messages will not be shown again. However, if the user aborts
the read, subsequent reads may bring up messages within the
thread.
S)top
Stop reading messages and return to the base prompt.
Invisible Options:
* Read/Scan Toggle
Toggle between reading and scanning; available to all users.
C)opy message
Copy this message to another base; available to SysOps and
CoSysOps (see SysOp MSG: COPY).
D)elete
Delete this message; available to SysOps, Sigops, and the sender
or receiver of the message.
E)dit
Edit this message: available to SysOps, CoSysOps, and base
creators. The editing will be done in the ANSI editor. If the
message is longer than 200 lines, it cannot be edited. All ANSI
editor commands are available.
F)ile
Create a text file of this message. A default filename will be
presented which may be changed. This feature requires that
DCIEXPRT.EXE be in the main DCI directory.
29
H)eader
Change this message header To, From, etc.; available to SysOps
and CoSysOps.
M)ove
Move this message to another base; available to SysOps and
CoSysOps (see SysOp MSG: MOVE).
U)ser Modify
After selecting either the TO or FROM user's name, the user's
Stats will be displayed. This is particularly useful when
responding to email. A user's settings can be checked and
modified without leaving the message bases. Once the Stats are
displayed, the message will be redisplayed so that it can be
replied to.
In addition to these commands, as the text of a message is being
displayed, entering a P will Pause the display, an S or pressing
the spacebar will stop the display (see Display Control).
Message Scan
The scan message command, S, allows the user to scan the headers
and text of messages within the base. The user will be prompted
to enter a range of messages to scan and then be prompted to
select how he wishes to search the messages. Entering a "Q" will
return the user to the base prompt.
Search options vary depending on the message format of the base,
although the SysOp has the ability to use any search option in
any base by pressing the SysOp READ key at the Search prompt.
Search options:
To
Scan for messages posted to a particular user. Enter all or part
of the user's handle.
From
Scan for messages posted by a particular user. Enter all or part
of the user's handle.
Both
Scan for messages both to and from a particular user. Enter all
or part of the user's handle.
Date
Scan for messages posted on or after a particular date. Enter
the date.
Subject
Scan for messages with a specified string in their subject.
Enter the string, case is unimportant.
30
Message Text
Scan for messages with a specified string in the text. Not case
sensitive (Registered versions only).
All
Scan all messages. This is the default option and will be
assumed if the user presses <ENTER> at the scan prompt.
After the user has specified how the messages should be searched,
the system will check each message within the range for a match,
displaying the "Looking" message if necessary. When a match is
found, the message header will be displayed followed by the Scan
Prompt.
Brief Scan
After entering a Scan option on a registered DCI board, the user
will be asked if he wishes a Brief Scan. If the scan option is
message text, the brief scan will display the message number and
the line of the message containing the text. Otherwise, the
Brief Scan provides a list containing Message Number, Status,
From, To, Subject, Position or Rating if appropriate, Original
Message Number, and Number of Replies.
Following the message number is a letter indicating message
status:
N - Not Received
R - Received (the default for messages to ALL USERS)
P - Protected
D - Deleted (will only display if the F5-Sysread is
active)
U - Unvalidated
The Brief Scan can also be invoked at the range prompt by
following the message number(s) with B (e.g. 100;120 B).
Scan Prompt
The scan prompt provides all the options of the Read Prompt, with
one difference. Rather than giving the user the option to R)eply
to the message, he may R)ead it. If the user reads the message,
he will then be able to make selections from the Read prompt.
Selecting N)ext at the read prompt will continue the message
scan.
31
MAIN: MISCELLANEOUS COMMANDS
Base Description
Pressing ^ (shift-6) at the base prompt will display a
description of the current base. This is the same description
that is displayed from the Base List. This option is
automatically added to users' Main Options.
List Users
This command, available from the Main Menu, displays an
alphabetical, two column list of all the user identities (system
name and handles) on the system. This display can also be paused
or stopped.
Operator Chat
Chat allows a user and the SysOp to type to each other. In chat
each character is sent as it is typed, as opposed to some systems
that only send a line at a time. DCI's chat uses word wrapping
and allows the SysOp to define the colors for both SysOp and user
input. The SysOp may elect to log the chat to a disk file for
future reference.
If System Chat Interrupts (see SYSOP: CONFIG) are turned on, chat
can be invoked in three ways. If the user enters an O, the
Operator Chat command from the Main Menu, the user will be asked
to enter the reason for the page which will remain displayed on
the screen and also recorded in the Activity Log. If the user
enters any input, the SysOp will be paged; otherwise, the page
will be aborted but the attempt will still be recorded in the
Activity Log. If the SysOp Available toggle is set to YES, an
alarm will sound to alert the SysOp while dots are slowly
displayed on the screen. If SysOp Available is set to NO, the
dots will still be displayed. The user can abort the page by
pressing any key. The SysOp may answer the chat page by pressing
any key on the local keyboard. If the chat request is not
answered, a highlighted "*C*" will appear on the status line and
the user will have the option of leaving feedback. If the user
leaves a message, it will be saved in E-Mail with the subject
listed as "Chat Request." The chat reason can be displayed on
the Status Line by pressing F1.
The SysOp can also invoke chat by pressing ALT-C or ALT-N. Both
of these commands interrupt the user's session on the board,
however, the ALT-N command is referred to as Nice Chat as it will
wait until the user is at a base or file prompt before breaking
in. The ALT-C command, SysOptus Interruptus, will break in as
soon as the command is entered.
Once chat is begun, a message will display telling the user that
he is in chat mode. Word wrapping in chat mode is based on the
user's screen width. A message to remind the SysOp of the
command for logging the chat to a disk file, "PgDn to open log
file", will appear on the SysOp's screen only. If you wish to
log a chat, the logging will begin as soon as the PgDn key is
32
pressed. The Chat Log will be marked with the current time and
date and the name of the user.
The message "Alt-B to beep user's return" also appears only on
the SysOp's screen. This is provided for SysOps who are chatting
with someone who says they'll be right back. Press Alt-B and DCI
will sound a bell when the user returns.
To exit chat mode, the SysOp must press the ESC key or the user
must enter Control-Q. If the user requested chat, 50% of the
time spent in chat will be credited to his account. If the SysOp
initiated the chat, the user's time will be credited 100%.
If you would like to make sure that no one breaks in on your
users via the Chat Interrupts, set Chat Interrupts (in
SYS:CONFIG) to OFF. This will prevent chatting from the local
keyboard until set to ON. This will also prevent Chat Pages from
being answered. Any attempts will be recorded in the Activity
Log.
Similarly, if you would like certain users to be able to override
the Chat Page Off, set the security level of Page Off Override
(in SYS:CONFIG). A user must have a security level equal to or
greater than this setting in order to force the page to sound
when it is turned off. The default setting is 255.
Time
This command displays the current time according to the computer,
in the format HH:MM a/pm. The system time can be changed by
SysOps and CoSysOps by using the SYSOP: BOARD Time command.
33
MAIN: NAVIGATION COMMANDS
Base List
The Base List, B on the Main Menu, lists all the bases that the
user has access to. A greater-than sign (>) after the base
number indicates that the base has new messages, an exclamation
point (!) indicates new messages addressed to the user, and a
caret (^) indicates a base the user has chosen to Ignore.
The Base List prompt allows a user to enter the number of a base
for information about the base, including the base creator and
base description, and to J)ump to the base. If the user enters
the number of a base that he does not have access to or that does
not exist, the system will beep and wait for correct input. The
user can also select the A)ll option which will list the base
format, purpose, and description of each of the bases the user
has access to.
"This is an Open base" indicates an open base and "Access to this
base is restricted" indicates a private base or one in which the
security level settings exclude Verified users.
As with most displays, the base list and extended listing can be
aborted by pressing the spacebar.
The J)ump command, explained in detail below, can be used from
the Base List prompt and the base description prompt. Entering a
question mark (?) will list an explanation of the commands and
symbols.
Jump to Base
The Jump command, J from the Main Menu, allows the user to move
to the base of his choice as opposed to the sequential navigation
of the Zip and <ENTER> commands. The user has three input
options at the Jump prompt:
Base Number
The user may enter the base number of any base that he has
access to, including any base he is Ignoring.
Base Name
The user may enter all or part of the name of any base that
he has access to. The system will search the base names
beginning at the next base until a match is found and the
user will then be moved to that base.
?
If the user enters a question mark, the Base List will be
displayed followed by the Jump prompt (rather than the
Description prompt that appears when the user selects Base
List from the Main Menu). The user may then enter a base
number or all or part of a base name and move to that base.
34
Where are My Messages
This command, from the Main Menu, displays information on bases
containing any unread messages addressed to the user, or, if
there are none, tells the user that no new messages are found.
This is the same display that users see when they first logon,
however it is updated, taking into account any messages they have
read since logging on.
The listing can be either Verbose (with base name and number of
new messages to the user) or Brief (base number only) by Setting
F)ull Where Msg in C)onfiguration.
Zip to New Messages
This is a navigation command available from the Main Menu. It
will take the user to the next unignored base (in numerical
order) that the user has access to and that contains new
messages. If none are found, the user will be returned to the
first base.
<ENTER> or <+> (Move to Next Base)
This will take the user to the next base (in numerical order)
that the user has access to and is not ignoring. <ENTER> is
functional only when the user has Hot Keys selected, though <+>
will work regardless of the Hot Key setting.
<-> (Move to Previous Base)
This command will take the user to the previous base (in
numerical order) that the user has access to and is not ignoring.
35
FILE: PROMPTS
Directory [#] Prompts
Most SysOp functions use this prompt, as do several user prompts.
If you press <ENTER>, the default directory (the number in
brackets) is selected. You may enter another directory number or
enter a Q to Quit. Entering a question mark will give you a
listing of the directory numbers and names.
Filename Prompts
These prompts behave a little differently depending on the
feature being used. Usually wildcards are acceptable, with the
exception of Private Downloads. In this case the user must type
in the exact file name.
In cases where the feature is directory specific (such as looking
for FileInfo in a particular directory), if wildcards are
entered, only that directory will be searched for matching
filenames. If the feature is not directory specific the
directories searched are dependent on the user's security level.
Only the SysOp has full access to the Private/SysOp directory, a
CoSysOp has access to the other private directories, and users
have access to only the open directories.
If a filename is entered without an extension, the extension .ZIP
is automatically appended to the filename. Entering the filename
followed by a period will not add .ZIP to the filename.
File Prompt
From the file prompt, as from the File Menu, the user may
download or view a file. The prompt also contains command
options for aborting the procedure (returning the user to the
File Menu) or continuing (the default).
If the user has selected a batch protocol, another option will
appear on the prompt line: B)atch Queue. This allows a user to
select files for later downloading. Once a file is added to the
Queue, it remains in it until the user downloads the file or
aborts the download process.
This prompt also contains two invisible commands. SysOps,
CoSysOps, and Directory Sigops may select F)ileinfo here and from
the SysOp menu. The SysOp may also invoke the K)opy command.
36
FILE: FIND FILES
Several commands allow a user to list files. Regardless of the
command, the user will be using the File Prompt at the bottom of
each screen and at the end of the listing. This prompt allows
the user to download, view, or queue a file, or continue or abort
the scan. When listing files in more than one directory,
pressing <ESC> will completely abort the listing.
The file information will be listed, including the filename, the
date the file was uploaded, the size of the file, and the file
description. All files have three lines of description except
files uploaded as Private to Directory #0 with a Designated
Recipient.
In some file listings, CoSysOps and SysOps may see P, H, R, or !
after a filename. P indicates a private file, H indicates an
invisible (or "hidden") file. When listing files in Directory
#0, an "R" indicates a Restricted file that has been Received and
an "!" indicates a Restricted file that has not been received.
The Designated Recipient will also be listed preceded by "DR ==>
".
List Directories
This command will list all the files in the specified
directories. The user may select the directories from the File
Directory Menu, enter A)ll to list all the directories, or enter
the directory number(s). More than one directory number may be
entered, but they must be separated by a semicolon. For
instance, to list files in directories 1, 2, and 7, the user
should enter 1;2;7. Only directories that the user has access to
will be listed. The File Prompt will display at the bottom of
each screen.
New Files List
The New Files command, N, allows the user to scan for files that
have been uploaded to the system on and after a specified date.
The user will be presented with a prompt, including the user's
last New File Date. If the user presses <ENTER>, this is the
date that will be used in the scan, or he may enter another date.
The Directory Prompt will then display. All options are
available: the user may enter A)ll, M)enu, or the specific
directory number(s). The system will search through all specified
directories looking for files uploaded on or after the designated
date. If any are found, the file's information will be
displayed. At the bottom of each screen and at the end of the
search, the user will get a File Prompt. Each time a user does a
New File Scan, his New File Date will be updated to the current
date.
Search Files
This command allows a user to search specified directories for a
text string or a file name. If wildcard characters (* or ?) are
entered, the system will search for matching file names only.
37
Otherwise, the system will search both file names and
descriptions for a match. When a match is found, the file's
information will be displayed to the screen. As in the New File
Scan, the File Prompt will appear at the bottom of each screen
and at the end of the search.
View File
This command allows a user to view the contents of a file, either
a text file or a compressed file, provided a viewer is available
for the file type. DCI allows for the internal setup of four
file viewers (ZIP, ARC, LZH, and GIF). Files ending with the
extensions TXT, MSG, LOG, DOC, BAT, PAS, ASM, C, H, ANS, and ASC,
can be viewed using DCI's internal file lister (no special setup
is required). See PROTOCOLS for more information.
38
FILE: TRANSFERS
File transfers allow users to exchange files with the system.
DCI supports open, private, include message, and SysOp-only
uploads and open and private downloads.
Transfer Prompt
Regardless of the specific transfer, once the file(s) are set up,
the Transfer Prompt will be displayed. This prompt offers the
following options:
[S]tart <protocol name> Transfer
This is the default command, the user may press <ENTER>
to invoke it. The protocol name is displayed to remind
the user which protocol to select on his end to transfer
the file.
L)ogoff after transfer
Transfer the file and then begin the autologoff
procedure which will log the user off the system if he
does not press a key within about 10 seconds.
A)bort
Do not transfer the file(s). The user will be returned
to File Menu prompt. If the user has selected files for
download, the board will ask the user if he wishes to
retain these files in the download queue. If so, when
the user next selects D)ownload, these files will appear
automatically.
Download
This command begins the process of transferring a file from your
system to a user's computer. This command is used to download
files from open directories. The Private Download command is
used to transfer files from private ones.
To download a file, a user must have a valid protocol. If the
user's protocol is no longer available, the system will prompt
him to select one. He will then be able to enter the name(s) of
the file(s) that he wishes to download. If he has selected a
protocol that supports batch transfers and has been defined as a
batch protocol (see PROTOCOLS), he may download more than one
file at a time.
The system will check that the file name entered by the user
matches the name of a file on the system and that the user has
enough time left to transfer the file. If the user is required
to maintain a ratio, the system will make sure that the download
of the file will not exceed the user's ratio.
If none of the conditions are met, the system will display a
message of explanation ("File not found", "Not enough time to
transfer..", "Ratio exceeded!"). In the case of a single file
39
download, the process will be aborted. In a batch download, the
user will be prompted to enter another file name. The current
file will not be transferred.
When the user is using a single file protocol, when one file is
selected for download the transfer prompt will be displayed.
With a batch protocol, the user will have to press <ENTER> at the
file name prompt to signify that he has finished selecting files
if the batch queue is not full.
As files are selected for download the filename appears along
with the size of the file and the number of estimated minutes the
transfer will take. If more than one file is selected, the total
size and time are also displayed. The time information at the
beginning of the prompts lists [ <time remaining> / <time
remaining after transfer> ] where the latter value includes
credit for time-free downloads.
Private Download
This command is used to download a file from a private directory.
This is the same as the Download procedure, with one important
difference: the user must know the exact file name. If the file
has a password assigned to it, the user will also have to type in
the password before the transfer will begin. (Private files that
have no password assigned to them will not prompt the downloader
for a password.)
A private file may also have a designated recipient. In this
case, to download the file, the user must be either the uploader
of the file or the designated recipient of the file.
Transfer Protocol
Before transferring a file, the user must either select a
transfer protocol from the list of defined protocols or use the
default Xmodem.
This command will display a message to the user, listing his
currently selected protocol, or "None", and ask if he wishes to
change it. Answering "yes" will take the user to the Protocol
Menu which lists all the active protocols available to the user
based on his security level. His selection is recorded in his
user account.
Upload
The Upload Command, U, allows a user to upload a file to the
system. The user will be asked to enter the name of the file and
the system will first check the Files Allowed listing and then
make sure that there are no other files with that name in any of
the file section directories. The user will then designate the
file as O)pen, P)rivate, for the S)ysOp, or an I)nclude message.
40
[O]pen
This is the default. The file will be placed in the
Directory #1, the Upload Directory. The user will be
asked to select the category (from a list of open file
directories) that the file should be later moved to. If
the user does not specify a category, the upload process
will be aborted.
P)rivate
The uploader will be asked if he wishes to restrict
download of the file to one specific user, the
Designated Recipient. If so, he will be prompted to
enter the user's name. The user will be asked to enter
a password. The file will be placed in a private
directory.
If the file does not have a Designated Recipient and
there is more than one private directory, the user will
be asked to designate the private directory to upload
the file to. Only those private directories that the
user has access to will be listed. If the user does not
specify a category, the upload process will be aborted.
I)nclude Message
The file will be uploaded to the Include Directory.
S)ysop
The file will be tagged with the SysOp File Password and
uploaded to Directory #0, the main Private Directory.
The user will then be asked to enter a description of the file.
Two lines, each of 40 characters, are allowed for files without a
Designated Recipient, and three lines of 40 characters each are
allowed for all other files. If the user fails to enter a
description the upload process will be aborted.
Once all the above information is complete, the user receives the
transfer prompt and may begin the upload. Upon completion of the
transfer, the system, based on the information from the protocol
program, will tell the user whether the transfer was successful
or not. If the transfer was successful, and Credit Uploads is
set to YES, the user's account will automatically be credited.
If Visible Uploads are set to YES, the file will also be visibly
listed in the directory it was uploaded to.
Designated Recipient Transfers
As explained under Private Download and Uploads, files may be
marked as having a Designated Recipient, which may be either a
user or a Group (see Group Accounts). These files are stored in
Directory #0.
Specifying a file as having a Designated Group Recipient
facilitates the distribution of files for business or security
purposes. A Mass Mailing or message in a private base can alert
all users to the existence of the file, the filename, and
password. Only those users specifically listed in the group text
41
file will be able to download the file. This prevents security
breaches caused by others reading over a user's shoulder or
reading communications program buffers or logs.
If an unauthorized person tries to download such a file, the
message 'Sorry, access to <filename> has been denied.' will
display and the notation 'Rstrd Dl att : <protocol>
<filename>' will appear in the Activity Log, indicating a failed
attempt at downloading a restricted file.
42
FILE: MISCELLANEOUS COMMANDS
Exit
This command will return the user to the Main Menu. If the user
has Hot Keys selected, <ENTER> will do the same. If the user has
aborted a download and there are files in the File Queue, he will
be reminded that exiting the file section will clear the queue
and given the opportunity of returning to the File Menu.
Kopy
This command is available to the SysOp from the File Menu, the
File Prompt, the AddNew command, and from individual file
listings in FileInfo. It allows you to copy a file from the File
Section to another directory or floppy diskette on your computer.
The command will not allow a file to be copied over another file
with the extension DCI. It also does not move file information
contained in the data files. This command is only for your
convenience. To move file information use the SysOp FILE MOVE or
MASS MOVE commands.
Remove File
If the user has previously uploaded a file, he can use this
command to remove the file from public view. This does not
delete the file or remove the file's entry in the data record.
This does rename the file, giving it the extension .REM or .R##
where ## is a number from 1 to 99 depending on how many times a
file with that name has been removed and is still in the DOS
directory. The SysOp and CoSysOp may remove any file; directory
sigops may remove any file in their directories.
Your Stats
This command will display the user's file statistics, including
the number of files and total kilobytes uploaded and downloaded,
and a line listing free downloads.
If the board participation is set at more than 0, the user's
relative participation will also be displayed using the
following:
Participation Description
100 - 200 Excellent
90 - 99 Good
75 - 89 Light
50 - 74 Low
1 - 49 Dismal
0 Zilch
When a user has called the board less than 6 times, he is given
"bonus points" when the relative participation is calculated.
43
The message "includes new user bonus" will appear after the
participation rating when this is the case.
If the user is not required to maintain a ratio, he will be
informed of this. Otherwise, the board ratio will be displayed
as will any text in the user stats section of ETC.MNU. See
RATIOS AND PARTICIPATION for more information.
This display is also shown to users who repeatedly try to
download and receive the "Ratio Exceeded!" message.
44
CONFIGURATION SECTION
The Configuration Menu can be reached by entering a C at the Main
Menu. From this menu the user can change most of his settings on
the system. The top two lines of the screen list the user's
number, first and last name, how many times he's called the
system, and the date of his last call. This information may not
be changed by the user. The menu contains the following options
which the user can change:
Menu/Prompts
The user can select whether the Main and File Menus will be
displayed and how the Message Read/Scan, File Section, and SysOp
Command prompts will be displayed.
The following levels are available:
Level Menus Prompt Commands
0 No None
1 No Minimal
2 No Full
3 Yes Full
When users log on as new, their Menu/Prompt Level is set at 3.
The X)pert command on both the File Menu and the Main Menu will
toggle the setting between levels 2 and 3.
Hot Keys
This setting is active at the Main, File, Configuration, and
Utility menus. If Hot Keys are ON, the user will not have to
press <ENTER> after entering a command.
Graphics
This setting determines whether or not the system will send
graphics characters and non-color ANSI commands to the user when
displaying messages and sections of MNU files. If the user has
ANSI Color ON and turns Graphics OFF, ANSI Color will be turned
off as well. Similarly, if the user has selected the ANSI editor
and turns Graphics OFF, the editor selection will change to the
Non-ANSI editor.
ANSI Color
This setting determines whether or not the system will send ANSI
color codes to the user's terminal. The user must be using a
communications program that either emulates ANSI.SYS or uses the
ANSI.SYS driver on his system. If the user has selected the ANSI
editor and turns ANSI Color OFF, the editor selection will revert
to the Non-ANSI editor.
45
Editor Type
If the user has Graphics and ANSI Color both set to ON, he may
choose to use the ANSI editor. The Non-ANSI editor may be
selected regardless of the other settings.
Editor Screen
If the user has selected the ANSI editor, he may customize the
background and text colors of the editor with this command. All
available color selections will be displayed and the user may
select one combination. If the user has selected the Non-Ansi
editor, this option will not display on the menu.
Password
If the user changes his password, it will be effective
immediately. The password may be 1 to 8 characters in length.
Only nongraphic characters are allowed in passwords. The system
will display the password after it is entered and ask the user to
verify that it is correct.
All user passwords are encrypted. No one, including the user and
the SysOp, will be able to view a user's password. If a user
forgets his password, a new password will have to be entered by
the SysOp (SYSOP: USER Modify), as the old password can not be
unencrypted.
Computer Type
The user may use this command to change his computer type
(IBM/compatibles, Apple/Mac, Amiga/Commodore, Other). This is
not used by the system, it is for informational purposes only.
Screen Length
The user's screen length is used by the system to determine how
many lines to display to the user before pausing the output with
a *MORE* or input prompt. The most common setting for screen
length is in the 20 to 24 line range. The user can disable
*MORE* prompts completely by setting this value to 0.
Screen Width
The system uses this setting to determine when to word wrap text
in messages being displayed or edited, and in chat mode. The
default setting is 80, as most terminals are 80 columns wide.
However, there are 40 and 60 column terminals in use. The system
will permit this setting to be in the 30 to 80 range.
Backspace Code
This is the character code that the system will send to the user
when it needs to tell the users terminal to backspace. Most
terminals use ASCII character #8, although some use #127.
46
Msg Threading
This is the permanent setting of the method used to display
messages to the user. With message threading set to YES,
messages will be shown according to the messages they are in
reply to. With threading set to NO, messages will be shown
sequentially.
Full Where Msg
This determines the listing that is displayed at logon and when
the user selects the W)here Msg command from the Main Menu. The
Verbose listing displays the base name and number and the number
of new messages to the user in that base. The Brief listing
displays just the numbers of the bases the user has new messages
in.
Identities
If the board allows handles and the user is allowed to use
handles, this option will appear on the menu. The user will be
presented with a list of his current handles (excluding the
system name which can only be changed with the SYSOP: USER
command), which he can alter, delete, or increase.
A new handle may not be a duplicate of another handle on the
system or match an entry in the Trash Name Log.
47
DOOR SECTIONS
Doors are external programs that can be accessed by the users of
your system. DCI supports most major BBS door programs. There
are two door sections available for use by the SysOp and CoSysOp
and two for the users of DCI systems. The main user door section
is accessed by entering * from the Main Menu; the file user door
section is accessed by entering * from the File Menu. The main
SysOp door section is off the SysOp Main Menu, and similarly, the
SysOp file door section is available from the SysOp File Menu.
If you do not wish for users to enter the user door areas, remove
the * from the new user options and from the individual records
of the current users, or set the Door Access Level above the
security levels of the users. In this way, you can have a main
door area and/or a file door area, or no doors at all. Only the
SysOp and CoSysOps have access to the SysOp door sections. In
addition, access to each door can be controlled by security
level, participation, and base access.
When a user enters a door section, all active doors with security
levels less than or equal to the user's security level will be
displayed. The user will be able to access any door that has a
participation level less than or equal to his system
participation. If his participation is too low, a message will
display informing him of this and a note will be made in the
Activity Log which includes the door's participation setting and
the user's participation.
CoSysOps and SysOps have an additional command on the doors
menus, S)ysop options. The SysOp Door Commands include A)dd,
M)odify, L)ist, P)urge, R)earrange, and S)ort.
Due to the wide variation in door software, you may not be able
to run all doors. A base and file directory devoted to
exchanging information and door programs is available on the
Nordevald Software BBS. Registered DCI SysOps receive immediate
access to these areas.
Modify and Add
After entering the number of the door you wish to modify, you
will be presented with a screen that contains several fields.
When adding a new door or overwriting a deleted record, you can
select the All option so that you are prompted for each field in
order rather than having to select them individually.
The door fields are:
Status
Deleted: the record is not used, and will be removed when the
data file is purged
Inactive: the door is not ready for access at the current time,
it will not be purged unless the information is not complete.
48
Active: the door is available for access.
Base #: by entering the number of a base in this field, only
people who have access to that base will see it listed on the
door menu and be able to access it. The door will be considered
Active.
File Name
This is the full file name (including extension) of the external
door program. It must be a file name with an extension of BAT,
COM, or EXE. The door program itself must be in the \DOORS
directory or in your DOS path.
Name
This is the name of the door that the users will see. It should
be 30 characters or less.
Access Level
This is the minimum security level necessary to use the door.
Parm Type
This is the type of door interface that the door program needs.
The menu includes:
0 - Included String
This will send the string stored in the parameter string
field verbatim. No interpretation will be done of the
string.
1 - DCI
For use with doors specifically written for DCI, usually no
additional parameters are necessary.
2 - Build String
This will tell the system to expand the string stored in
the parameter string field before it is sent to the
external program.
3 - Create PCBOARD.SYS file (PCBoard).
4 - Create DORINFOx.DEF file (RBBS).
5 - Create DOOR.SYS file (GAP).
6 - Create CHAIN.TXT file (WWIV).
7 - Create CALLINFO.BBS file (WildCat!).
The last five types create files needed by different types of
doors. These files contain information about the user that the
49
door program needs to operate properly. Some require a parameter
string as well as the file. If this is the case, add this in the
parameter string field.
If a door modifies the user's information by changing the data in
the CALLINFO.BBS file, Nordevald Software's CALLUSER utility will
update the user's record upon return to the BBS. See
CALLUSER.DOC for complete information.
Support is included for PCBoard version 14 and above. Doors that
require only PCBOARD.SYS to be created will run. Some PCBoard
doors claim to be PCBoard 14 compatible, but still require the
presence of other PCBoard files (which DCI does not create).
There are utilities available to create these extra files.
8 - Create Custom file.
In addition to creating standard door interface files, this
option allows creation of a file containing specific
information. The Send Parms field defines the contents of
the file.
The first parameter of the Send Parms string must be
/CF<filename>. This is the complete name of the file to
create. If no path is given, it will be created in the
\DOORS directory.
Any %Parameters following it will be translated and added
to the file, one per line. If you need to send additional
parameters on the command line to the external program,
enter /STOP on the Parms line and enter the command line
parameters after it.
For instance, to create a file named DOOR.TXT containing
the user's name (%N), the user's time left (%L), and also
pass the comport (%P) and baud rate (%B) as command line
parameters, the Send Parms would be:
/CFDOOR.TXT %N %L /STOP %P %B
To create DOOR.TXT in the Main DCI directory, enter:
/CF%ZDOOR.TXT.
Similarly, to create DOOR.TXT in the MNU directory, enter:
/CF%ZMNU\DOOR.TXT.
Parameter String
Include any additional parameters the door may need in this
string.
When you modify the parameters, you will be shown the actual
entry (what you entered) and the translated entry (how DCI will
expand the parameters when sending them to the external program).
50
In this way you can be certain that the necessary information
will be sent to the door program.
Door Description
An optional 40 character description of the door program that
will be displayed at the right of the Door Name on the menu.
ANSI Only
If a door is set to ANSI only, only users with ANSI Color
selected will be able to access the door. Others will not see
the door as an option on their menu.
Local Only
If a door is set to Local only, only users on locally will be
able to access the door. This is particularly useful for SysOp
doors that call programs that do not work over the modem.
Remote Only
If a door is set to Remote only, only users online remotely will
be able to access the door. This will probably be used rarely,
though most often with SysOp doors that call batch files using
CTTY redirection to work over the modem.
When you exit the modify area, you will be asked if you wish to
save the current changes to the door record. S)ave will save any
changes you made to the record.
Submenus
To create a submenu, modify an entry and set the parmstype to
100. The filename will indicate the data file for the records in
the new door menu. As with a regular door entry, access to the
menu can be controlled by security level, participation, and
message base access.
List
List provides a listing of all doors in the door data file of
that section. This is a sample listing:
File name Status Sec Parmstype PFr Display Name
1. DCIVOTE.EXE Active 60 DCI 0 The Ballot Box
2. TESTGAME.EXE Inactv 255 PCBoard.SYS 0 Testing NewGame
3. OLDGAME.COM Dele'd 60 DOOR.SYS 50 Charades
4. DATEGAME.EXE Act 40 60 CALLINFO.BBS 20 Dating Game
51
Sec is the security level required to access each door and Pfr is
the participation factor.
Note that Door #4, the Dating Game, is linked to access to base
40.
Purge
Purge removes all door records with a status of deleted from the
door data file (see Sort below).
Rearrange
Rearrange allows the SysOp to change the order in which the doors
are recorded in the data file and hence the order in which they
appear in the menu.
The Rearrange Menu allows you to swap the positions of doors and
optionally save the new arrangement or abort it.
Sort
Sort arranges the door records alphabetically by the door names.
Both Purge and Sort are done by an external utility,
DCIDSORT.EXE. This program must be located in your DCI
directory.
Special Situations
Some doors require their own directory and a file, such as
PCBoard.SYS which is created by DCI. DCI creates all such files
in the DOORS directory. A batch file can be used to move the
user information file to the particular door's directory and then
execute the door program. For instance, if you have a door named
SOMEGAME.EXE that must be in a directory named GAME and also
requires DOOR.SYS to run, define the door with a filename of
SOMEGAME.BAT and Parm type 5, Create DOOR.SYS. Drop to DOS and
create the directory GAME off the DOORS subdirectory and create
the following batch file in the DOORS subdirectory:
FILENAME: SOMEGAME.BAT
copy DOOR.SYS GAME
cd GAME
SOMEGAME
cd..
Some doors written to be used with other BBS software need files
in addition to the ones that DCI creates. There are numerous
utilities available (several are on the DCI Home Board) that will
create these files. The utility can be called from a batch file
that then calls the door program.
52
Selecting Door Programs
The atmosphere and users of your system will determine the
specific door programs to look for. However, you must make sure
that the programs are well behaved before allowing users access
to them.
Make sure all door programs meet the following criteria:
The program monitors carrier.
The program returns control to the BBS immediately if a user
drops carrier.
The BBS recycles correctly after a user that has accessed the
door logs off.
The program works correctly from both the local keyboard and
remote.
The program executes quickly when a user selects it from the
door menu.
The door correctly monitors the user's time and will not let a
user stay in the door beyond his BBS time limit, or a time
limit you specify.
Door programs that return exit codes and are well documented
are preferred. In case of a problem, these features will help
you determine what the problem is.
Whenever you set up a new door, test it thoroughly before
allowing users to have access to it. This testing should include
dropping carrier while in the door to make sure that it returns
control to the board.
53
INFORMATION SECTIONS
The Information Sections allow users to select text files to read
from a menu and to reread the main and file bulletins, both
permanent and one-read only.
There are separate information sections available from the Main
and File Menus. Each is modified in the same manner. The first
eight text files of each section are contained in a MNU file.
The Main Info text is contained in INFOMAIN.MNU and the File Info
text is in INFOFILE.MNU.
The main information section is predefined when you initially set
up DCI. This is for your convenience. Decide what text you wish
to include in the first two sections and follow the steps below
to modify it.
Each Info Section contains the same commands.
Modify
The command Modify will prompt the SysOp for the number of the
bulletin to modify and then display the bulletin title. If you
do not want the title displayed, enter an asterisk (*).
If the bulletin number is greater than eight, you will also be
prompted for the separate file name of the bulletin. Make sure
the file is in the MNU directory, or the bulletin entry will be
deleted.
The Modify command only changes the Title and Filename (if the
bulletin number is above 8). It does not modify the text. To
change the text, use the SYSOP: FILE command Edit or edit the
file from DOS using a text editor. (see Display Files for
specific information on the MNU files.)
To increase the number of bulletins beyond eight, enter the next
higher number when prompted for the bulletin number.
Purge
Use the Purge option if you have deleted bulletins with numbers
greater than eight and wish to renumber the remaining bulletins.
Submenu
To create a sub-menu, modify an entry and at the Title Prompt
enter $<title>. The $ tells DCI that this is a submenu title.
You will then be prompted to enter the filename. <filename>.DCI
will contain the setup for the files contained in <filename>.MNU.
Make sure you indicate a unique filename.
54
UTILITY SECTION
The Utility Menu, accessed by entering U at the Main Menu,
contains options for adding and modifying message bases,
displaying a list of recent callers, the Ignore Base Utility, The
Customize Base List Utility, the Log to Disk Utility, and the
Search User Utility. Each is explained in detail below.
Adding Message Bases
Use this option to add a base to the system. The option will
only appear on the menu if the user's security level is equal to
or greater than the security level necessary to add a base.
Bases are added sequentially. If a base has been deleted, the
next base added will replace it.
The first base is always reserved for E-Mail. All messages added
in it will automatically be set to private. The second base must
always remain an open base. With these exceptions, there are no
limitations on any other bases on your system.
When a user other than the SysOp enters this area, the Add a Base
section of ETC.MNU will be displayed. The user will then be
prompted to enter the name of the base. Pressing <ENTER> at this
point will abort the process and return the user to the Utility
menu.
Each base has fields that define it. The Creator will be
prompted for:
Base Name
The base name can be as long as 30 characters. Both upper
and lower case are allowed.
Creator's Handle
If the system allows handles the creator of the base may
specify one of his handles to be listed Creator of the
base. If handles are not allowed this will default to the
user's system name.
Private
DCI bases can be open or private. You have a large degree
of control over users' access to the base regardless of how
you set it up.
If the base is open, the SysOp can make access dependent on
security level by changing the base security level defaults
(0-255). All users who fall within the security levels
will have automatic OPEN access to the base, including new
users provided their security level is in range. Otherwise,
55
all users will have immediate access to the base.
If the base is private, access can also be made dependent
on security level by changing the defaults. All users who
fall within the security level will have automatic PRIVATE
access to the base, but new users will not, regardless of
their security level. If you do not change the default
security levels of the base, you can give specific users
access from the Modify Base Menu.
Only SysOps and CoSysOps can change the security level
settings of a base. When a regular user adds an open base,
all users have access to it. If a regular user adds a
private base, s/he will have to grant access to users
individually.
Network
This field should be set to NONE. On networkable versions
of DCI (future releases), the network setting will
determine how message header information is accessed and
stored.
Read Only
Normally this is set to NO. This field should be set to
YES if a user is going to set up an information base. This
will disable any user (other than the SysOp and the creator
of the base) from entering messages in the base.
If you wish to allow several users to maintain an
information base, you can set the base up as read only, and
then modify the accounts of individual users to allow them
write access to the base.
Allow Handles
If the board does not allow handles, this field will be set
to NO automatically. Otherwise, the creator can decide
whether or not to allow users to use handles in the base.
56
Message Format
This determines how the headers will appear on messages
posted in the base. DCI offers 12 different message
formats:
Standard:
To, From, Subject, Date, Time, status, replies
Anonymous:
Message text only (no header), replies to user indicated by an
asterisk under dividing line
Information:
Subject, Date, replies to user indicated by an asterisk
under dividing line
Gaming:
To, From, Subject, Date, Time, Open/Priv, status, optional
replies
Debate:
To, From, Subject, Date, Time, Position, status, replies
(Position: Pro, Con, Undeclared)
Narrative:
<user> adds..., optional replies
Dialogue:
<user> says to <user>, optional replies
Action:
<user> <action>, optional replies
Story:
Message only, No reply option, Page #
57
Secret Ballot:
Subject, Position, replies to user indicated by an asterisk
under dividing line (Position: Pro, Con, Undeclared.)
Five Star Rating:
To, From, Subject, Date, Time, Rating, status, replies
(Rating: 1 to 5 stars, Overrated, or the dreaded Big Boo.)
(Registered versions of DCI only.)
Secret Rating:
Subject, Rating, replies to user indicated by asterisk under
dividing line (Rating: 1 to 5 stars, Overrated, or the dreaded
Big Boo.) (Registered versions of DCI only.)
Dated Dialogue:
<user> says to <user>, Date, Time, optional replies
(Registered versions of DCI only.)
Dated Narrative:
<user> adds..., Date, Time, optional replies, replies to user
indicated by asterisk (Registered versions of DCI only.)
Letter:
To <user> [text] From <poster>; the text has indented left and
right margins (Registered versions of DCI only.)
Purpose of Base
This field indicates the purpose of the base. It is
displayed as part of the descriptive listings available
from the Base List.
The following purposes are available: Discussion,
Information, Gaming, General, Amusement, Storytelling. The
base purpose does not have to match the message format.
Description
The description is a brief summary of the base. It should
give users an idea of the creator's intentions for the
base.
58
Header Color
This color is used in the message header. How this affects
the display is dependent on the message format:
Standard - dividing line, prompt
Anonymous - dividing line, prompt
Information - dividing line, prompt
Gaming - dividing line, prompt
Debate - dividing line, prompt
Narrative - FROM, prompt
Dialogue - FROM/TO, prompt
Action - FROM/ACTION, prompt
Story - Page number, prompt
Secret Ballot - dividing line, prompt
Five Star Rating - dividing line, prompt
Secret Rating - dividing line, prompt
Dated Narrative - FROM, prompt
Dated Dialogue - FROM/TO, Date, Time, prompt
Letter - TO, Date, Time, Subject, FROM
Text Color
This field allows the creator of the base to choose the
default color of the message text. If the user uses no
color codes in the message, the text will be displayed in
this color. If the user changes colors, the \NO (normal)
color code will be this text color.
Display Filename
If you would like to attach a display file (which will be
displayed above the base prompt), enter the file name here.
Do not add the .MNU extension, the system will do that
automatically. The file must be located in the \MNU
subdirectory. (see DISPLAY FILES)
Bases do not have to have display files. The field may be
left blank.
Low and High Security Levels
This field will only be displayed to the SysOp and CoSysOps
of the board. When a user adds a base, these values
default to 0 and 255 respectively.
By changing the value of either of these, you can restrict
the access of the base to a certain group of users. If the
base is private, no new users will have access to the base
regardless of security level.
If users have already been added to a private base before
these values are set, and they do not fall within the new
range, they will be removed from the base. The SysOp and
the creator of the base cannot be removed from the base.
59
The base settings will be displayed before the base is actually
added and give the base creator the option to Abort the procedure
entirely.
Several other settings may also be made:
Ignorable
Whether or not users can ignore the base. The default is
YES. This option is only available on bases above Base #2
and the SysOp is the only one that can change this setting.
Movable
Whether or not users can "move" the base location on their
customized base list. The default is YES. This option is
only available on bases above Base #2 and the SysOp is the
only one that can change this setting.
Show Rec'd Date
Whether or not to display the date that the message was
received by the addressee. The default is NO. This option
is only available for bases using the Standard, Debate, and
Letter message formats.
Show Rec'd Time
Whether or not to display the time that the message was
received by the addressee. The default is NO. This option
is only available for bases using the Standard, Debate, and
Letter message formats when Show Rec'd Date is set to YES.
Allow Replies
Whether or not replies are allowed to individual open
messages in the base. The default setting is YES, which
allows the creation of message threading. In some bases,
such as a role playing base, this may not be desired. If
this is set to NO, users will be able to reply to private
messages. This setting also does not effect the ability of
users to A)dd messages from the base prompt.
This setting is always NO in bases using the Story format.
It is optional with Gaming, Narrative, Dialogue, and Action
formats.
Creation Date
The date the base was created, also displayed in the base
description from the Base List menu.
DOS Path
The location of the .HDR and .MSG files for the base. The
default is the path of the current base. Only SysOps and
cosysops can change this setting.
60
Invisible options:
Change Base Number
By pressing #, the base number may be changed. The default
base number is the first available undefined base. This
command is available only when a new base is created by the
sysop.
Change Base Visibility
By pressing *, the local visibility of private base may be
changed. The default is that the message and edit screens
are blanked. This option is not available for the email
base and only the SysOp can change setting.
Modify Base
Once a base is created, it may be modified by the SysOp, CoSysOp,
or base creator. The Modify option appears on the SYS: BASE menu
(for SysOps and cosysops) and on the Utility Menu where it is
specific to the base that the user is in when he selects U from
the Main Menu.
A listing of all the base information will be displayed and each
can be changed, with several exceptions as noted in the base
fields explanations above. Also, only the SysOp can modify the
display format of Anonymous, Information, and Secret Ballot
bases. This adds a degree of protection to users posting in
these bases. See Adding a Base above for details on the various
base fields.
If an Open base is changed to Private, all users will lose access
to the base. Changing a Private base to Open will allow all
users access. If the Read Only status of a base is changed, only
those users with current access to the base will be effected.
If the Security Level settings on a base are changed, you will
have the option of being prompted to confirm changes in users'
access. If you elect to be prompted, the system will as you to
confirm or deny each user who is either added or removed from the
base.
In addition to the initial set up of the base, one more option is
available, to Modify Users of a private base. Selecting Modify
Base Users will display the following options:
Add user to list:
Enter the user's name (partial names can be entered) and
the user will be given immediate access to the base.
Delete user from list:
Enter the user's name (partial names can be entered) and
the user's access to the base will be removed.
61
List users as current:
If the base creator has less than CoSysOp access this will
list only users with read/write or read only access to the
base. For SysOps and CoSysOps the listing also includes
users who have been locked out of the base or who have
chosen to ignore the base.
Customize Base List Utility
Users may rearrange the order of bases as they see them by using
this utility.
If a user swaps Base #3, The Third Base, and Base #4, The Fourth
Base, his base list will show:
3. The Fourth Base 4. The Third Base
He may now jump to 3 to get to The Fourth Base.
When Zipping, if there are new messages in both bases, the user
will first zip to The Fourth Base and then The Third Base. The
same order applies to using the <ENTER>, +, and - commands from
the base prompt.
The customization is saved to the user's account and in no way
changes message pointers, base access, or access to doors and
file areas. The SysOp modifies these as before, though has the
option of also viewing the user's customized base list and
reseting it to the default system base list.
Bases marked as immovable cannot be rearranged on a user's base
list, nor can bases 1 and 2. A user also cannot swap an existing
base with a non-defined one.
The C)ustomize option is also available from the Base List
prompt, though with not as many options or help information.
Ignore Base Utility
This utility, also available from the B)ase List prompt, allows
users to remove bases from their Zip navigation of the board, or
to restore a base that they have previously ignored.
Normally the Zip command takes the user to the next base
containing unread messages. However, it will skip ignored bases.
An ignored base is designated by a caret (^) on the Base List.
The user can still J)ump to the base and can post in it. Users
are prohibited from ignoring the first two bases, and cannot use
this utility to gain access to bases that they did not have
previous access to.
62
Log to Disk Utility
This option provides the user with a simple way of making a log
file of messages. The user tells the board which messages he
would like to receive and then opens a log file via his term
program. The user will have the option of logging all new
messages, or all new messages addressed to him, in all bases that
the user has access to and is not ignoring. No prompts will be
displayed and the user has the option of automatically being
logged off the system when the process is complete.
The user can P)ause or S)top the display. If the display is
stopped, the user will have the option to stop logging entirely,
go to the next base and continue logging, or to continue logging
in the current base.
NonStop Read
NonStop defaults to OFF when a user logs on the system. If the
user turns it on, there will be no pauses between messages in a
base, nor will *MORE* prompts display. It will remain active
until the user either turns it off or logs off the board.
Users may also temporarily activate Nonstop read at the Message
Range Prompt, or permanently by setting Screen Length to 0.
Recent Callers List
This option will display a list of recent callers starting with
the last caller to the system. The user may pause (P) or stop (S
or spacebar) the display. This is actually a display of the
information in the Call Log. Only information on users who did
not visit surreptitiously will be displayed to regular users.
Regularly purging the log will keep this list to a reasonable
length.
If the user has less than CoSysOp access, the listing will only
contain the user's system name and location. CoSysOps and SysOps
will also see the time and date of the call. A tilde (~) before
a user's name indicates a surreptitious visit.
When a user views the list, his entries will be highlighted.
Search User Utility
The Search User Utility prompts the user to enter the name, or
part of the name, of the user to search for. If the user is
found, his city, state, and the date of his last call is
displayed.
If a user with less than CoSysOp level security searches for
information on a user with CoSysOp security or greater, the
message "Information is not available." will be displayed.
63
MAIN SYSOP COMMANDS
SysOp Commands are available from both the Main and File Menus by
typing 1. Other SysOp commands are available from the Door and
Information menus and the Message Prompt lines. These are
covered in detail in the appropriate sections (see DOORS,
INFORMATION, MESSAGE READ).
Selection 1 from the Main Menu will take you to the Main SysOp
Menu. There are six options with suboptions on this menu:
B)ase Add
List
Modify
Remove
C)onfiguration Board Info/Directories
Modem Setup
System Setup
Transfer Section
New User
Color/Screen
Miscellaneous
F)iles (LOGs, MNUs) Edit
Purge
Search
View
Color and ANSI View
M)essage Copy Message
Delete Received E-Mail
File to Text
Header Modify
Move Message
Purge Messages
S)ystem Bulletin Reset
Events
Rebuild Index
Date (submenu)
Time (submenu)
Disk Space (submenu)
PrintScreen Enable/Disable
U)ser Add New User
Delete User
Modify User
Group Modify
Search User File
*) Main SysOp Door Menu
<ENTER> -- Exit
Each of these sections is covered in detail on the following
pages.
64
SYSOP: BASE
The Base section is where you can view and modify the message
bases' setup information.
Add Bases
See the UTILITY SECTION, Adding Message Bases, for details.
List Bases
This command displays a list of all the message bases and their
definitions.
Here is a sample listing:
# Base Name MSGS P R H N LSL HSL HCL TCL D FRMT PRPS
1 E-Mail 327 Y N Y N 0 255 106 107 Y Stnd Gnrl
2 General Chat 169 N N Y N 0 255 106 107 N Stnd Disc
3 Music 233 N N Y N 0 255 106 107 N Stnd Disc
4 Good Books 197 N N Y N 0 255 106 107 N Stnd Disc
5 Software 13 N N Y N 0 255 102 106 N Dial Disc
Total Messages: 939 in 5 bases.
MSGS - Total messages in the base
P - Private: Y)es or N)o
R - Read only: Y)es or N)o
H - Handles allowed: Y)es or N)o
N - Networked: Y)es or N)o
LSL - Low security level
HSL - High security level
HCL - Header color
TCL - Text color
D - Display file: Y)es or N)o
FRMT - Format
PRPS - Purpose
The listing may be stopped by pressing S or the spacebar.
In addition to the above listing, two others are also available.
Here is a sample of the second listing:
# Base Name M I D T R Directory
1 E-Mail N N Y Y Y C:\DCI\MSG
2 General Chat N N N N Y C:\DCI\MSG
3 Music Y Y N N Y C:\DCI\MSG
4 Good Books Y Y N N Y C:\DCI\MSG
5 Software Y Y N N Y C:\DCI\MSG
65
M - movable
I - ignorable
D - rec'd date displayed
T - rec'd time displayed
R - replies allowed
Directory - DOS dir where base's .HDR & .MSG files are stored
Here is a sample of the third listing:
# Base Name Created By
1 E-Mail 08-01-91 JOE E. SYSOP
2 General Chat 08-01-91 JOE E. SYSOP
3 Music 08-01-91 JOE E. SYSOP
4 Good Books 08-01-91 JOE E. SYSOP
5 Software 08-02-91 BENNY FILES
Modify Base
This is the same command as the M)odify Base option on the
Utility Menu. It is covered in detail in the Utility section.
Remove Base
Use this command to delete a message base from the system. You
will be asked to confirm the deletion before it is actually done.
When you remove a base, the message (.MSG) and header (.HDR)
files are not deleted. This is to guard against accidently
deleting a base. You can delete them from DOS.
66
SYSOP: CONFIGURATION
The Configuration section is where all the setup information on
your board can be changed. The menu displays several areas, and
each area contains several items. The first area, Board Info,
can only be accessed by users with security levels of 255.
Board Info
Board Name
The board name is printed to the screen during user logon and as
part of the title of the Information Section. It should be forty
characters or less in length.
SysOp
This field identifies the user number of the SysOp of the system.
This field is used to determine the user to notify when feedback
and E-Mail is addressed to SysOp. The SysOp's system name will
be displayed in the editor header.
Board Location
This field should reflect the name of the city and state or
province where your BBS is located.
Country
If this field is set to Canada, province, rather than state,
information will be requested.
Board Directory
This is the directory name where DCI.EXE will be residing. All
subdirectories will be created off of this directory. If you
change this field after you have initially run DCI_INST, you will
need to make sure that the new directory has all of the
appropriate files and subdirectories for the DCI program. The
subdirectories \DOORS, \LOGS, \MNU, and \MSG must be
subdirectories of this directory. The file section directories
may be located anywhere.
67
Upload Directory
This is the full directory name of where uploaded open files are
stored. The default value of this field is \FILE. If this field
is changed, you will need to make sure that all files are copied
to the new directory (XCOPY \FILE\*.*) and the path is changed in
the File Section (DirInfo, directory 1).
Access Password
This is the password required when granting a user temporary
SysOp status and dropping to DOS if a user with less than SysOp
access is online.
Sysop Files Password
This is the password that is given to all files uploaded to
SysOp. No one else will be able to access files protected by the
password.
CoSysOp Security Level
When users log on, their security level is compared to this value
to determine if they have CoSysOp access, which gives them access
to certain functions on the board. In order for a CoSysOp to use
most SysOp options, he must have an access level of equal or
greater value than this field, and have 1 in his Main Command
Options.
Private Board Logon
Note: Use this only if you want to severely restrict access to
your board! This is an 8 character (or less) string of text that
must be entered before the logon screen will appear when a user
calls. There is NO prompt for this string and characters entered
by the caller will not be echoed.
If this field is empty ("<NONE>" appears as the setting), the
logon screen will appear normally when a caller connects. The
default is <NONE>.
Private Base Display
If set to YES, any private bases that have local visibility set
to YES will display on the local screen.
If set to NO, all private base message and edit screens will be
blanked ( DEFAULT ).
Pressing Alt-Q ( "Quick, hide that screen!" ) will toggle this
setting from the local keyboard.
68
Sound
If this is set to NO, the DCI program will not make audible beeps
or sound alarms except when SysOp Next is turned on or a user
requests a chat and the SysOp Page is turned on. When set to
YES, all alarms and beeps (including when a user makes an input
error) will be heard.
Number of Calls
This is the total number of calls your system has received. It
is displayed to users at logon, and incremented every time a user
logons the board.
Activity Log Settings
These settings allow you to tell DCI whether or not to record the
following information in the Activity Log:
Invalid logons
Msg read & scan info
Prompt and editor beeps
Info section entries
Ignore base/user search
Chat information
File section entry/exit
File section misc.
File section sysop info
Door entry/exit
Door miscellaneous
Next event info
Miscellaneous main menu info
All sysop logins
Only remote sysop logins
It is suggested that you record all activity until you are more
familiar with the operation of DCI.
Chat Settings
If SysOp Chat Page is set to YES, the DCI program will alert you
by sounding an alarm if a user wants to chat. When set to NO, no
alarm will be sounded, although the user will still receive the
chat request beep on his terminal. The system gives you
approximately 15 seconds to answer a chat. Regardless of this
setting, an unanswered chat will be indicated by a *C* on the
Status Line.
The Chat Page Off Override is the security level necessary for
users to override the Chat Page Off. A user must have a security
level equal to or greater than this setting in order to force the
page to sound when it is turned off. The default setting is 255.
Chat Interrupts must be ON for you to initiate chat or answer a
chat page. If you would like to make sure that no one breaks in
69
on your users to chat from the local keyboard set this to OFF.
Any attempts to chat while this is set to OFF will be recorded in
the Activity Log.
The Always Log Chats setting determines whether or not the text
of chats will automatically be recorded in CHAT.LOG.
Modem Setup
See MODEM SETTINGS for more information on setting your modem dip
switches and default settings for nonvolatile random access
memory.
Initialization
This is the initialization string that will be written to the
modem every time the board recycles. This string MUST contain
the commands X4, Q0, and S0=0 (i.e., ATS0=0 M0 X4 V0 Q0).
In order to allow 300 and 9600 baud callers, you must have V1 in
your init string. This tells the modem to use verbal result
codes. If 300 baud calls are not accepted nonverbal result
codes, including those invoked by the HST &A2 command, will be
recognized by DCI.
If you have any problems with callback verification of new users
or the board does not seem to hang up correctly, try adding the
command that tells the modem to reset on a drop of DTR (Hayes
command &D3, please consult your modem manual as all modems that
claim to be Hayes compatible do not respond the same to this
command) and the command that tells the modem that DCD on
indicates carrier (Hayes command &C1).
If you are using a maximum baud rate of 9600 or more and users
are having difficulty aborting displays, adjust the size of the
modem buffer (HST register 15) and make sure that your modem is
set to handle hardware handshaking.
The command H0 should not be in the initialization string.
Local Init
This is the initialization string written to the modem when
someone logs on via the local computer. It should take the phone
off-hook so that users will get a busy signal. Adding the M0
command will silence the modem speaker (i.e. ATH1 M0).
Hangup String
This is the string written to the modem to disconnect from the
user. ATZ or ATH0 are recommended. Some modems may require that
this command be surrounded by pause characters (e.g.,
~~~ATH0~~~).
70
Com Port
This field should reflect the number of the serial port that your
modem is connected to on your computer (1-4). If you enter
either 3 or 4, the system will give you the opportunity to enter
non-standard Address and IRQ information. The defaults will be
listed at the prompt. If you have any doubts, enter the
defaults.
Minimum Baud
This is the lowest baud rate at which callers may logon to the
board. If you do not want to allow 300 baud callers, set this
field to 1200. If this value is greater than the maximum speed,
the maximum speed value will be changed.
Maximum Baud
This field should reflect the highest baud rate that the modem
can operate at. Setting this value below that of Minimum Baud
will reduce the minimum speed.
If you have an HST modem and are using the &B0 command in the
modem initialization string, do not set the maximum baud rate
higher than 9600.
If you are using the &B1 command in the modem initialization
string, set the maximum baud rate at 19200 or 38400 and set
Locked Baud to YES.
With the maximum baud set to higher than 9600, you will still see
CONNECT 9600 messages. The modems cannot connect at higher
speeds than 9600, though the link rate will be the maximum baud
rate you have set.
Locked Baud
Set this value to YES if you are using a modem that supports
locked baud operation and you have set the modem to operate at a
set link rate, otherwise it must be set to NO.
Tone Dial
Set this value to YES if the board's data line allows tone
dialing. If set to NO the modem will pulse dial.
71
Terminal Mode
This option allows you to send commands directly to your modem
and receive the modem's responses. Several special commands are
available and listed on the status line:
/HELP - display Help Screen.
/INIT - send initialization string to modem.
/LOCAL - send local init string to modem.
/HU - send hangup string to modem.
/SPEED - change speed at which port is
initialized.
/CHANGE - make new settings permanent.
/EXIT - exit terminal mode, return to BBS
These commands allow you to send predefined modem strings to the
modem or change your current settings. To change a setting,
enter the command followed by an equal sign (=) and the new
setting. For example, /LOCAL=ATH1 M0 or /SPEED=2400.
This is intended only as a means of checking your modem setup
strings and the modem settings (NRAM, et cetera). It is not
meant to be a telecommunications program.
System Setup
Events Allowed
This field should not be set to YES unless you have defined
events that are ready to run (see EVENTS). When this option to
set to YES, every time a user logs on the board will check to see
if the user's time is going to be limited by an upcoming event
and similarly the board will check for a pending event while
waiting for a call.
Open Doors
Setting this field to YES indicates the presence of external door
programs. In order for the users to access the door section an
asterisk (*) must be included in the users' Main Command Options.
(see DOORS, MODIFY USERS)
Handles Allowed
DCI will support eleven handles per user. This will allow users
to use multiple names on the board, while maintaining them in a
single account. If this field is set to 0 only the real first
and last name of the user will be allowed; setting it to 1 or
more will allow the user to select handles in addition to his
real name. If you want users to log on with their real names,
yet still allow the use of handles, set this option to 0, and set
New User Verified Handles to a higher value.
72
Security Level to Add Base
This is the minimum security level required for adding message
bases to the system. If a user's access is less than this he
will never be shown the menu option for adding a base (see
UTILITY SECTION).
Security Level to Door Menu
This is the minimum security level required to access the public
doors sections of the board if installed.
Security Level to Add Handles
This field can be used to allow only certain users to add
additional handles. Set this field to the minimum security level
that you will allow to have handles.
Enforce Daily Time Limit
If this field is set to YES then users will be restricted to
their given time limit per day. If it is set to NO, users will
receive the full amount of their allotted time per call. (see
TIME)
Allow Overtime Usage
If no events are due and the SysNext key has not been pressed,
this setting determines whether users reading messages will be
logged off as soon as they run out of time or allowed to continue
until they return to a base prompt.
Allow Recent Call List
This setting determines whether or not users can view the list of
Recent Callers from the Utility Menu.
Allow User Search
This setting determines whether or not users can use the User
Search from the Utility Menu.
Mass Mail Security Level
This is the security level necessary to use Mass Mail.
Mass Mail Limit
This is the number of copies of a message which may be mass
mailed at once (does not apply to SysOps and cosysops).
73
Transfer Section
Open File Section
Setting this field to YES indicates the presence of a file
transfer section. In order for users to access the file section,
F must be included in the users' Main Command Options.
Security Level to Transfer Menu
This is the minimum security level required to access the file
section of the board if one has been installed.
Check Upload Disk Space
If this field is set to YES, the system will make sure that there
is at least 1000K available on the drive containing the upload
directory before allowing a file to be sent to the board. If it
is set to NO, no checking for free space will be done. If you
are sure you have plenty of space, particularly if you have a
large hard drive, turning this off will increase system
operating speed.
File Section Ratio
If this field is set to greater than 0, the users will have to
maintain an upload ratio in order to download files. If set to
10, a ratio of 1 upload to 10 downloads will be in effect.
File Ratio Basis
If this field is set to File Size (K), the ratio will be
determined by file size. If it is set to Files Transferred, the
ratio will be determined by the number of files uploaded and
downloaded. This field is only active if the file system ratio
is set to greater than 0.
Participation Factor
The value of this field determines the amount of participation in
the message bases that you expect of users. It is calculated in
with the file ratio to penalize less active users and reward more
active ones. It can be used to grant access to door programs
also.
74
Upload Time Compensation
This is the percentage of upload transfer time that you wish to
credit to the users. This can be as low as 0, no credit, or as
high as 200, which will reward the uploader with twice the amount
of time spent uploading a file.
Visible Uploads
If this field is set to YES, all uploaded open files will be
available for downloading to anyone who has access to the file
system. If this field is set to NO, newly uploaded files will
not be displayed in the file lists.
Credit Uploads Immediately
If this field is set to YES, the user will be given immediate
credit for a file transfer (adding the file size to the user's
Uploaded K field and increasing the Files Uploaded field). If it
is set to NO, then the SysOp will have to grant the user credit
manually via FileInfo.
Upload Integrity Check
If this is set to YES, DCI will execute ICHECK.BAT after a file
is uploaded. This batch file should call software that performs
integrity checking and returns a nonzero exit code if the file(s)
does not pass the integrity check. A sample ICHECK.BAT is
included in the DCI package.
Upload Virus Check
If this is set to YES, DCI will execute VCHECK.BAT after a file
is uploaded. Like the integrity checking, this batch file should
call a virus detection program that will return a nonzero exit
code if the file(s) fails the test. A sample VCHECK.BAT is
included in the DCI package.
Allowed File Extensions
If you do not wish to restrict the types of files uploaded, leave
this field blank. Otherwise, enter the extensions that you will
allow (i.e., ZIP.DOC.EXE).
If you wish to allow the upload of files with no extension, you
must add ". " (a period followed by a space) to the files allowed
setting. You must add this _before_ another extension, for
instance:
Good : . .ZIP
Nope : .ZIP .
75
Invalid File Message
If you are allowing only specific files, this is the message that
is displayed to a user who is attempting to upload a file with an
extension that is not allowed. For instance, if Files Allowed is
set to ZIP, the message might read: "Please upload only ZIP
files."
New User
New User Registration and Callback Verification are covered in
detail in NEW USER REGISTRATION. A new user is considered
Verified if added by the SysOp or if verified by callback. All
other new users are considered unverified.
Allow New Users
This field should be set to YES if you plan to run an open board.
If you are running a business oriented BBS and/or wish to
restrict access to only those added by the SysOp, set this option
to NO. Users who attempt to log on the board when it is not
accepting new users will be allowed to enter feedback to the
SysOp.
Verified Security Level
This is the security level that will be granted to users who are
added by the SysOp or verified by callback.
Verified Daily Time
This is the time limit that will be granted to new users added by
the SysOp and those verified by callback.
Verified Handles
This is the number of handles a verified user is allowed to use
on the system. You may wish to restrict this initially and
increase the user's handles later.
Verified Main Options
This field should contain the Main Menu Command Options that will
be available to verified users (see MAIN MENU).
Verified File Options
This field should contain the File Menu Command Options that will
be available to verified users (see FILE MENU).
76
Unverified Security Level
This is the security level that new users who have not been
verified by callback or added by the SysOp will receive.
Unverified Daily Time
This is the time limit that new users who have not been verified
by callback or added by the SysOp will receive.
Unverified Handles
This is the number of handles an unverified user is allowed to
use on the system. You may wish to restrict this initially and
increase the user's handles later.
Unverified Main Options
This field should contain the Main Menu Command Options that will
be available to unverified users (see MAIN MENU).
Unverified File Options
This field should contain the File Menu Command Options that will
be available to unverified users (see FILE MENU).
Local Callback Verification
If this field is set to YES, new users whose data line numbers
are a local call will be called back to verify them during
registration.
Allow Long Distance Users
This field should be set to YES if you want to allow long
distance callers to register on your system. If set to NO, long
distance callers will be given the option of leaving feedback to
the SysOp but will not be entered into the user file.
Board Area Code
This field is used in conjunction with LDPHONE.LOG and
GOODAREA.LOG to determine if a registering user's data line is
long distance to your system. Enter your Area Code.
Dialing Prefix
The prefix necessary for the board modem to dial out. The
default is none.
77
Dialing Suffix
The suffix necessary for the board modem to dial out. The
default is none.
LD Callback Verification
If this is set to YES, the board will attempt to callback
registering users who are long distance. To keep costs to a
minimum, if the user does answer the call, they will only be
online until they have entered all the new user information. The
board will then explain that they must call back for access to
the board and log them off.
Long Distance users will also only have one chance to complete
the callback. This is to prevent abuse and high long distance
bills.
The default is NO.
Callback at Every Login
If set to YES, all users will be callback verified at EVERY login
before allowed access to the system. Only users with the Extra
Option Force Callback set to NO will not be called back.
This option is included for systems where security is very
important, such as in business settings. The default is NO.
LD Callback at Login
If Callback at Every Login is set to YES, this option allows
callback of long distance numbers. In this instance, the board
will be paying the long distance charges of the user's session
online.
The default is NO.
Color/Screen
Color Sets
This displays a menu of all the color settings of the board.
Direct Video
If this field is set to YES, DCI will write to the screen using
direct screen writes. If set to NO, it will use standard DOS
function calls to write to the screen. Direct screen writes are
much faster than the DOS counterpart, but may cause problems on
some machines which are not 100% IBM compatible or when using
multitasking software. If direct video is set to NO, the Status
78
Line will not appear on the bottom of the local screen.
Miscellaneous
External Editor
If you want to use an external editor to edit files from the
SYSOP: FILES menu, enter the complete filename (including
extension) of the editor here. This editor cannot be used to
edit, add, or delete messages. If you do not define an external
editor, DCI's internal ANSI editor will be used.
External Editor Remote Use
If you defined an external editor and the editor will work from
remote (over the modem), set this to YES. Otherwise, set it to
NO and you will be able to use the external editor from the local
keyboard only and DCI's ANSI editor from remote.
External Viewer
If you would like to use an external text viewer when viewing
files from the SYSOP: FILES menu, enter the viewer filename
(including extension) here. If you do not define an external
viewer, DCI will use internal routines to display the files.
External View Remote Use
If you defined an external viewer and it will work over the
modem, set this to YES. Otherwise, set this to NO and DCI will
use internal routines to display files both locally and remotely.
Main Door Menu Title
This is the title for the Main Door section of your board.
File Door Menu Title
This is the title for the File Door section of the board.
Auto-Logon File Name
The Auto-Logon File enables you to specify a program to run after
the user has entered his name and password and before the Main
Menu is displayed. Leaving this field blank will indicate that
there is no program to run.
79
Auto-Logon File Parameters
This field should only be used if an Auto-Logon program is
specified. It contains any parameters that the program may
require. (see PARAMETERS)
Auto-Logon New Users Only
Set this to YES if you have defined an Auto-Logon Program and
want it to run for new users only, such as a questionnaire
program. If set to NO and an Auto-Logon Program is defined, it
will run every time a user logs on.
Auto-Logoff File
The Auto-Logoff File enables you to specify a program to be run
after the user has entered the G)oodbye command from either the
Main or File Menu and before the Logoff screen is displayed.
Leaving this field blank will indicate that there is no program
to run.
Auto-Logoff File Parameters
This field should only be used if an Auto-Logoff program is
specified. It contains any parameters that the program may need.
(see PARAMETERS)
Auto-Logoff New Users Only
Set this to YES if you have defined an Auto-Logoff Program and
wish it to run on users' first call only. If set to NO and an
Auto-Logoff Program is defined, it will run every time a user
logs off.
Execute LOGOFF.BAT
If you would like to run a program after every logoff, set this
to YES and create a file named LOGOFF.BAT in the Main DCI
directory to call the program(s). The most obvious use for this
is to call a quote program so that each user receives a new
quote.
After a user hangs up, the system will take the modem offhook,
execute LOGOFF.BAT, put the modem back on hook, and wait for the
next caller.
The default is NO.
Network/Record Number
These fields will be used in future versions of DCI. Network
should be set to NO and Network Record Number should be set to 0.
80
SYSOP: FILES
When F)iles is selected the View Menu is displayed. Pressing
<ENTER> brings the full Files Menu. This menu provides for the
viewing, editing, searching, and purging of text files on your
system.
If you select Edit, Search, or View, the following lists will be
displayed:
A)ctivity, !) Alert, C)hat, F)ailCall, R)ecent Callers, *) more
B)ulletins, E)tc, H)elp, I)nfo, L)ogonoff, M)enu, Re(G)ister, *
L(D)Phone, Trash N)ame or P)hone, T)ransfers, U)ser, O)ther
The lists provide one-key access to most of DCI's Log and MNU
files. At any list, you may enter any letter, or * to display
the next list. For instance, at the first list prompt, you can
enter H to access HELP.MNU. You may also select O)ther to access
a file that is not on one of the lists (you will be prompted to
enter the full path and file name).
When using the DCI internal editor or viewer, all files edited,
viewed, or searched from remote on the SYS: FILES menu will be
blanked on the local screen. Pressing F6 on the local keyboard
will allow the text to be displayed locally as well.
At "M)ore, N)ext, F)ull screens, A)bort:" and "M)ore, N)ext,
A)bort:" prompts, "C" will indicate Nonstop/Continuous display
mode. This will remain active until the SYS:FILE area is exited.
If you would like easy access to other text files from this menu,
create a textfile named DEFFILE.DCI in the DCI directory. This
text file can contain up to 10 filenames (including full
pathnames) that you can pull up from the SYS: FILES menu to view,
edit, purge, and search by entering the number of the file. The
first file listed in DEFFILE.DCI can be accessed by pressing "1",
the last file by entering "10".
At Edit, Search, & View prompts, pressing S will bring up the
DEFFILE.DCI file.
Color Test
This displays all the DCI color codes.
Ansi View
This option allows you to display any file, though it is
specifically designed for testing ANSI screens and files that
contain display codes to make sure that they will display
correctly. An external program, DCISHOW, is available free from
Nordevald Software for this purpose as well.
81
View File
Select this option to view a text file. If an external viewer is
defined (SYSOP: BOARD), it will be used to display the file
selected; otherwise, the system will display the file using
internal routines.
Edit File
Select this option to edit a text file. If an external editor is
defined (SYSOP: BOARD), it will be used to edit the file;
otherwise, the internal ANSI editor will be used.
Purge File
This option creates a dated back up copy of a text file. It is
used primarily for the Activity, Call, and Failcall logs. The
back up copy file name will contain the first two letters of the
original file name followed by the current date in the format
MMDDYY. Up to 99 backups of a file can be made on the same date.
Each will be stored separately in files with the number of the
backup in the extension if more than one backup is made of the
file on that date.
Purging the Call Log in this manner will leave the last three
entries in the current Call Log. Any other file will be
completely cleared.
Search File
Search allows you to search for a string of text in the file.
Enter the search string at the prompt. If the string is found in
the file the line containing the string and the next nine lines
of the file will be displayed followed by the prompt "M)ore,
N)ext, F)ull Screens, A)bort:". M)ore or <ENTER> will display
the next ten lines of the file, N)ext will search for the next
occurrence of the string, F)ull Screens will display a full
screen of information (rather than just ten lines) before pausing
with another prompt, and A)bort will stop the search.
82
SYSOP: MESSAGE
Header
Use Change Header when you need to change information stored in a
message header. This procedure is similar to the Change Header
command at the Message Read Prompt.
When you are prompted to enter a message number, the total number
of messages in the base is displayed in parentheses.
Below is a sample listing of a message header:
Message number: 21
1. To : TYPICAL USER - U#15 H#0
2. From : ANOTHER USER - U#143 H#3
3. Date : 02/20/1989
4. Time : 12:58:58
5. Subj : Long time, no read...
6. Open/Priv : O
7. Status : N
8. Rec'd Date: 08-01-91
9. Rec'd Time: 23:26
10. Moved : 0
11. Reply : 16
12. Threads : 1. 30 2. 38 3. 42 4. 0 5. 0 6. 0 7. 0 8. 0 9. 0
S>ave changes
N>o changes
This is message 21 from Another User (whose user number is 143
and "Another User" is the user's 3rd identity) to Typical User
(user number 15, system name). It's an O)pen message that has
N)ot been received. The message is a reply to message number 16,
and has three replies (messages 30, 38, and 42).
Any of these fields can be changed though caution should be used
when changing the Reply and Threads fields.
Message status can be set to P, protected. The message can then
only be deleted by the SysOp by deleting from either Change
Message or Delete Message but will not be deleted in a mass
delete or purge.
The Move field is the base number that the message has been moved
from. A zero indicates no move and can be used to remove the
Moved Message from a message display.
After selecting either S)ave changes or E)xit (which does not
save changes), the next prompt is "C)hange base, S)ame base,
E)xit:". Select C)hange base if you wish to modify the header of
a message in another base, S)ame base if you wish to modify the
header of another message in the current base, or E)xit to return
to the menu.
83
Copy/Move Message
These commands are also similar to the C)opy and M)ove message
options on the message read command line with the exception of
the base and number prompts and the ability to move more than one
message.
After entering the number of the base to copy/move the message to
and verifying the base, "Message has been copied/moved" will
appear to let you know that the process was successful.
Messages that are moved from one base to another will contain a
message saying "[ Moved from base #, <base name> ]". If you do
not want this displayed, you can modify the message using either
H)eader at the message prompt or SYSOP: MSG H)eader and change
the Moved From Base to the current base number.
Delete Received Email
This command allows you to delete messages in E-Mail that have
been received. You may have to do this weekly to increase the
speed of searches for messages in the E-Mail base. You will be
prompted to enter a range of message numbers to delete. It is
suggested that you do not delete through the last message in the
base as users often prefer to keep a reply available for future
reference. When you delete the messages, purging the base will
renumber the remaining messages.
File
This option will write a range of messages to a text file. After
selecting the base, the system will prompt you for the range of
messages and the format. The following formats are available:
Full DCI headers
Abbreviated DCI headers
UTI (Universal Text Interface)
If Full or Abbreviated DCI headers are selected, the next prompt
will ask if threads should be followed.
The system will then display a default filename for the text
file. To use this filename, simply press <ENTER>, or enter
another filename. Entering no filename will abort the procedure.
The message to text file options require DCIEXPRT.EXE in the DCI
directory.
Purge
This option allows you to run DCIPURGE without exiting the board.
You will be prompted to enter the command line to be sent to
DCIPURGE. You may list one base or several (#,#,#), including a
range of bases (#-#). You may also combine these (e.g., #,#,#
#-#).
84
SYSOP: SYSTEM
Bulletin Reset
This option will reset the main and/or file section one-read
bulletin pointers of all users. This option should be used if a
new main or file bulletin is added or if either has been updated
so it will be displayed to the users.
Events
Events are covered in a separate section later in the
documentation.
Rebuild Index
Rebuild the index if the L)ist Users display is corrupted or not
alphabetized. When users have been deleted, the indices will
automatically be rebuilt.
Date Set
Available from submenu (M)ore). Reset the system date. Do not
do this from Drop to Dos.
Free Space
Available from submenu (M)ore). Check free space on disk drives.
Time Set
Available from submenu (M)ore). Reset the system time. Do not
do this from Drop to DOS.
PrintScreen
Available from submenu (M)ore). Disable or enable the
PrintScreen key. This can also be done with a command line
switch.
85
SYSOP: USER
Add User
Use this option to add a new user to the system. When the user
logs on the first time he will be presented with the Final Text
of REGISTER.MNU and prompted to verify his name, phone numbers,
and date of birth. When adding a user, if you elect to add the
user's phone numbers you will be notified if a user's phone
number is a duplicate or long distance and you will have the
option to continue adding the user if you wish.
Delete User
Use this option to delete a user from the system. You can also
delete users via the S)earch option and the M)odify option. The
Search option is more convenient if you plan on deleting more
than one user. However, if you wish to add a user's information
to the Trash Logs, you must use this option or manually add the
Trash entries yourself. When selecting users to delete via the
Modify or Search options, the users are not deleted immediately;
they are added to the delete queue and then deleted en masse when
you are done.
Modify User
Use this option to modify one user record at a time. At the
prompt you can enter the user's number or all or part of the
user's system name.
CURRENT STATS of TYPICAL USER
1. SYSTEM NAME : TYPICAL USER #15
2. FIRST NAME : JOHN D. FIRST CALL : 11/25/1988
3. LAST NAME : DOE D. LAST CALLED : 08/08/1991
4. CITY : SOMEWHERE D. FILE DATE : 08/01/1991
5. STATE : FL X. TIMES CALLED : 121
6. VOICE PHONE : (555)555-5555 L. TIME LIMIT : 60
7. DATA LINE : (555)555-5555 T. TIME TODAY : 24
8. PASSWORD : PASSWORD H. HANDLES : 10
9. BIRTH DATE : 03-28-67 E. ANSI EDITOR : YES
V. VERIFICATION : Local CB B. BULLETINS : M-YES F-YES
S. SEC LEVEL : 60 P. PARTICIPATION : 50/100
O. EXTRA OPTS R. RATIO : NO
U. UL/DL : U:25/308 D:31/519 F:4/202
M. MAIN OPTS : ABCDFGHIJLMNORSTUWXZ*?
F. FILE OPTS : DEGHLNPRSTUVXY
J. JOT A NOTE : Good user!
A. BASE ACCESS I. IDENTITIES
Z. CLEAR OPTIONS K. DELETE USER
N. NO CHANGES *> UPGRADE -> DOWNGRADE
Any of the stats can be changed by entering the appropriate
number or letter.
86
The System Name is the user's system name followed by the user
number. When a user's system name is changed, the TrashN Log and
user file are checked. First name and last name are the user's
real name, as entered during registration. They are not
accessible by regular users.
Validation explains how the user gained access to the system
(SysOp added, Callback, et cetera).
There are several Extra Options. The first one allows Extra 5
Minutes When Overtime. The default for this setting is YES. The
Extra 5 Minutes means that even if a user runs out of time and is
logged off, the system will give him 5 minutes of time for a
later call. This is to allow users to log back on to leave or
read an important message.
The second option, Force User Info Update, will tell the system
to prompt the user at his next logon to verify his system name,
phone numbers, and date of birth. The default for this setting
is NO.
The third Extra Option, Always Force Callback, will prevent a
user from accessing the board without successful callback
validation at EVERY logon. The default is NO.
The fourth Extra Option, Force Random Callback, will tell the
system to randomly force callback verification when the user logs
on before he gains access to the system. The default is NO.
The next option, Set Time to 0 After Next Call, will tell the
system to set the user's time to 0 AFTER the next logon
preventing user from logging on again. The default is NO.
The final option, Messages Auto-validated, tells the system that
all messages the user enters are automatically valid. If this is
set to NO, the user's messages will have to be manually validated
by the sysop, cosysop, or base creator. The default is YES.
The dates record the user's first logon, the last time the user
called the board, and the date of the last new file search. If
you change a date, you can enter it in any reasonable format and
the system will change it to the proper format.
Times Called records the number of times the user has logged on
the BBS. If the user was added by the SysOp and has not yet
called this will be set to zero.
The Time Limit is the user's time limit per call or per day
depending on System Time Restrict. Time Today reflects how much
time the user has remaining for the day.
Handles is the number of handles the user may use. It is
independent of the System User Handles setting. If you do not
allow any handles on the system, you can still allow selected
users to have them. Similarly, you can set an individual user's
handle setting to below that of System User Handles.
87
Bulletins reflects whether or not the user has viewed the current
M)ain and F)ile one-read bulletins. If the setting is Yes, you
can toggle it and the bulletin will be displayed to the user
again.
Participation contains two values. The first is the user's
posting participation. Every time a user enters a post of more
than a few words, this value is incremented up to a maximum of
255. The second value is the user's relative system
participation on the board, his actual participation compared to
the board participation that you expect. The first value is
"bonus" points added when the relative participation is computed.
The relative participation is based primarily on messages read
though security level and messages posted are figured in as well.
You can change the first value, but not the second. It is
provided to give you an indication of the user's activity on the
board. SysOps and CoSysOps will have a relative participation of
100% regardless of any other settings.
Ratio is whether or not the user must maintain a ratio of uploads
to downloads in the file section. The UL/DL entries consist of
U)ploads, D)ownloads, and F)ree downloads with number of files
listed first followed by number of kilobytes.
The Main and File Options are the Command Letters that the user
can enter at the respective menus. These can be toggled on and
off by selecting the M or F, or cleared by selecting Z (only the
G)oodbye command will remain). Use the Z option with extreme
caution. It will clear the options on a corrupted file.
Identities will list any handles a user has selected, and give
you the option of deleting or modifying them.
Jot a Note allows a 40 character note to be entered into each
user record. User Search can be used to search for strings of
text in this field.
Base Access lists the user's available bases in the following
format:
Base number [current message pointer] Base Access
1. [315] Open -- access 2. [168] Open -- access
3. [ 80] Open -- sigop 4. [151] Open -- read only
5. [228] Open -- access 6. [139] Private -- access
7. [ 90] Ignore -- user choi 8. [ 0] Private -- no access
9. [ 0] Base not defined
88
The prompt "[ Base # or #;# to change, U, R, S, ? ]: " allows the
following options:
# - change base #
#;# - change bases # through #
? - Display command help
0 - Exit
U - Display User's Custom Base List
R - Reset User's Custom Base List to System Default
S - Display System Base List
At the prompt "Base # to change:", enter the number of the base
if you wish to change the user's access or pointer of a base, or
simply press <ENTER> to continue or 0 to stop.
If you enter a base number, you will then be asked to enter the
new access level or select P to change the user's pointer in the
base. Entering a question mark will list the available access
levels.
The K (kill) command adds the user to the delete queue. If you
wish to add the user's information to the trash logs, do not use
this option; use D)elete from the SysOp USER command line
instead.
Pressing asterisk (*) will upgrade a user's security level, time
limit, allowed handles, and main and file command options to
those you have set for Verified users. This does not change a
user's base access. This can also be done while the user is
online by pressing ALT-V provided that the user's time limit and
security level are below that of the Verified user settings.
Pressing minus (-) will downgrade a user's settings to those set
for Unverified users. This does not change a user's base access.
When searching the user file (detailed on the next page), the
option to Quit Global Scan will also be available.
89
Search User File
Use this option to view and change user records based on a
specified field in the user record. Select a search field from
the listing and then enter the search criteria at the prompt.
All user records that meet the criteria will be displayed.
The search fields appear in the following listing:
1. System Name 17. Times Called
2. First Name 18. Daily Time Limit
3. Last Name 19. Bulletins
4. City 20. Computer Type
5. State 21. Validation
6. Voice Phone 22. Date of Birth
7. Data Phone 23. Extra Options
8. Security Level 24. Ul/Dl ratio
9. Editor type 25. Uploads
10. Main Command Options 26. Downloads
11. File Command Options 27. Free Downloads
12. User number 28. Board Participation
13. Altnames 29. Msg Participation
14. Handles 30. First Call Date
15. Base access 31. Last Call Date
16. Note 32. Last File Date
Select the field you wish to search and then enter the range
within that field or search string at the next prompts.
The next prompt asks how you want the matching users' info
displayed:
[P]rompt, F)ull display, L)ist, A)bort:
Prompt - the user's name will be displayed followed by
(Y/N/A) where Y displays the user stats screen, N
goes to the next user, and A aborts the entire
process.
Full - the user's stats are displayed
List - a list of primary handles of all matching users
Abort - do not continue with Search.
You can search for all users who have only called once, all users
who are long distance (validation field), all users who haven't
called in three months (last call date) and so forth. The user
records will appear as they do for Modify User giving you the
ability to modify the record, delete the user, or just view the
information.
If you accidently delete a user, you can pull up the user's
record by Searching for the user's system name. To restore the
90
record, enter the user's first and last names and then Rebuild
the Index (SYS: SYSTEM menu).
Group Modify
Use this option to modify user records based on security level.
Modifications include number of handles, file and main command
options, file ratio, participation, security level, and time
limit.
Select the field to modify. At the next prompts, enter the
lowest and highest security levels of the users that you wish to
modify. If you change your mind, simply press <ENTER> and the
process will be aborted.
If the field is Handles, Participation, Ratio, Security Level, or
Time, you will now be asked to enter the new value.
If you have selected File or Main Command Options, you will be
asked whether you want to add, remove, or replace options. The
first two modify the users' existing options, while replace
deletes them entirely and replaces them with the new options.
After the records are modified, a display will tell you how many
records fell within the range of the security level limits you
set and how many records were actually modified.
91
FILE SYSOP COMMANDS
DCI maintains the file section in close concert with DOS. Each
DCI file section directory should be a separate DOS directory.
The DOS directory will contain the actual files listed in the
file section directory's data file and the data file itself.
When a file is uploaded to the system, it's information is
automatically added to the data file of that directory. However,
if you DOS copy a file to a directory, you must tell the system
to add the information to the data file.
AddNew File
If you have placed a file in a DOS directory, use this option to
add it to the data file. You will be prompted with "Autofind?".
If you answer Yes to the prompt, you can enter a file mask (such
as, TP*.*, the default is *.*) and you will be prompted with the
filenames that match the mask and aren't found in the data file.
The (Y/[N]/A/D/V) prompt:
Y)es, add the file's info to the data file
N)o, next file
A)bort procedure
D)elete file (with confirmation)
V)iew file (provided a viewer is available)
K)opy file
If you answer "No" to the Autofind prompt, you will be prompted
to enter the name of the file (wildcards are acceptable). If a
file is found, you will then be prompted for a password if the
directory is private, and a description of the file.
DIRectory INFOrmation
DirInfo allows you to alter file directory data, create new
directories, list the existing directories, and remove deleted
directory info from the data file.
All Directories
A listing of all file section directories will be displayed
showing the directory number, name, DOS directory, # of files,
whether or not a display file is selected, whether or not the
directory is private, and the message base designation. This
gives you a quick overview of the setup of your file section.
Create Directory
This option adds a new file directory to the file section. You
will be asked to enter the name of the file directory, the DOS
directory it will be located in, and the filename of the data
file. If the DOS directory does not exist, it will be created.
92
If any of this information is not entered, the directory will not
be created. If it is created, it will be initially defined as
private. You will have the opportunity to modify the settings or
abort before the record is saved.
Purge Deleted Directories
This process will remove any deleted file directory information
from the data file. File directories are marked as deleted by
changing their name to an asterisk (*).
Individual Directory
This is the default selection. You will be asked for the
directory number. You will then be presented with a listing of
the file directory fields which you can modify.
Directory Fields:
Number
Determines the order of the directory names in the
Directory Menu. If you change the number, R)earrange
directories.
Name
This is the directory name displayed on the Directory
Menu. It should be 30 characters or less in length.
If you want to delete a directory change the name to *
and then use the DirInfo Purge option to remove the
directory's information from the data file and renumber
the remaining file directories.
DOS Dir
The Actual DOS directory where the files in this
directory are located.
Creator
A user may be assigned as the Sigop of a file
directory. The sigop will have access to the data on
the files within the directory (FileInfo from the File
Prompt) and be able to Remove files from the directory.
Created
The date the directory was created.
Filename
This is the name of the directory data file. The
system will add the extension .DCI to it.
Total Files
This field reflects the total number of files contained
in the data file. If you do not feel that this value
is correct, select this option and press <ENTER> to
have the system calculate the Total Files for you.
93
CD ROM
If the directory is on a CD ROM drive, set this field
to YES. This tells DCI not to write to the directory.
The directory's data file will be stored in the
Transfer Path directory.
Description
Five lines of 40 characters each that describe the
directory.
Display File
If you wish to attach a display file to the directory,
enter the name of the file here (the system will add
the .MNU extension) and place the file in the MNU
directory.
Security Level
The Security Level necessary to access the directory.
Private
This field can be toggled depending on whether the base
is private or open. NOTE: If you choose to have more
than one private directory, it is best to locate other
private directories after all the public directories.
Msg Base
This value determines access to the file directory.
The default for this field is 1, indicating an open
directory that accepts uploads.
If the message base field is set to 2, it will not
appear in the listing of directories when a user is
asked to select the permanent directory for an uploaded
file. This is a way to restrict uploads of particular
types of files.
If this value is set greater than 2, the directory will
be considered private, allowing access to only the
users who have access to the corresponding message
base. For instance, if you enter 15, only users who
have access to base 15 will have access to this file
directory. Others will not even see it listed on the
File Directory Menu. This is a way of tying users'
access to file directories to their access to message
bases. If the user does not have access to the message
base, he will not have access to the file directory
either.
Reset NewDirs
This will set the NewDir setting on all the files in
the current file directory to the current directory
number.
94
Zap Data File
This option should be used ONLY in an emergency. This
will delete the data file and you will have to begin
again, A)dding new files. Use this option only if you
have accidentally deleted the directory or the files in
it.
FILE INFOrmation
The system retains information on each file in the file section
in data files. You can view and change this information. There
are several options for finding the file information that you
want.
All Files
If you select A)ll files, each filename in the record
will be presented to you. Answering Y at the prompt
will show you all the information, N skips to the next
file, A aborts the procedure, B moves back to the
previous file, and V allows you to view the file.
Individual File
Enter the filename at the prompt (wildcards are
accepted) to pull up the record of the particular file.
Search Files
Pull up file records based on a search of criteria you
specify in one of the following fields:
1. Filename 11. Not Private
2. Before Date 12. Visible
3. On Date 13. Not Visible
4. After Date 14. Removed Files
5. Uploader 15. Deleted Files
6. NewDirectory 16. Not Credited
7. Password 17. Restricted download
8. Size 18. Restricted download rec'd
9. Times Downloaded 19. Restricted download not recd
10. Private 20. Designated recipient
If you select Visible, Not Visible, or Not Credited as
the search field, you will be able to toggle these
options from the prompt line.
If you select Visible, an "H" will appear on the prompt
line so that you can toggle the file to Not Visible
(Hidden).
If you select Not Visible, a "U" will appear on the
prompt line so you can toggle the file to Visible
(Unhidden).
95
If you select Not Credited, a "C" will appear on the
prompt line so that you can credit the uploader's
account.
If you have Credit Uploads set to NO, searching the
upload directory and any private directories that you
allow files to be uploaded to periodically for not
credited files will allow you to easily credit files.
You can view each file before granting credit if you
wish.
Verify Files
This option will check all the files in the directory
data file to make sure that they actually exist in the
DOS directory. Optionally, any errors will be recorded
in the Activity Log.
File Fields
Filename
This is the name of the file. If you change the
filename and it is found in the DOS directory, the DOS
filename will be changed to the new filename. If it is
not found, or the name you select is a duplicate of an
existing disk file, you will have the option of
changing the filename in the record. Use this option
with caution!
This filename should correspond with the name of the
file on disk. To prevent inconsistencies do not drop
to DOS to rename files, copy them from one file section
directory to another, or delete them. You may
accomplish all these tasks from within DCI which will
allow DCI to keep the data file information updated.
Date
When a file is uploaded, the date is set to the current
system date. You can modify this. Pressing <ENTER> at
the prompt will automatically enter the current system
date for you.
Size
This is the actual size of the file in kilobytes. If
this entry is not correct, selecting size will update
it.
New Directory
This is the file section directory to move the file to
for permanent storage. It is used in Mass File Moves.
After a file has been moved this will change to the
number of the current directory.
96
Uploader credit
This field indicates whether or not the uploader has
received credit for uploading the file. If you select
this option, you will be asked if you wish to credit
the account, and if so, the uploader will be given
immediate credit for the file. You may also similarly
remove credit from the uploader's account.
Uploader
This is the system name of the user who uploaded the
file. You may change this by entering all or part of
the user's handle.
Description 1, 2, and 3
These are the three lines of the file's description.
They are contained in separate fields so that you can
change one without changing the other. If a file is
has a Designated Recipient, the third line of
description is used for this information.
Visible
Whether or not the file information is visible to the
users.
Private
Whether or not the file information is private.
Private file descriptions are not visible but should be
moved to a private directory for transfer protection.
Password
If the file is private it should have a password.
Files uploaded to the SysOp are given the default SysOp
file password set in the Board Config section. Open
files do not need a password.
Times downloaded
This field is updated by DCIFCNT.
Rstr'd/Rec'd
Restricted refers to a file that has a Designated
Recipient. Received indicates if this file has been
downloaded by the Designated Recipient.
FileInfo Listing Commands
Delete the File
Only users with SysOp access can delete a file. This
is an actual delete. The file will be deleted from the
hard drive. If the file is not found in the DOS
directory but is found in another directory, it will
not be removed from the disk but the filename in the
record will be changed to <DELETED>.
97
Kopy the File
Copy the file to another directory or disk. This does
not move the file's information. This is for the
SysOp's convenience only. Use this command to copy a
file from the file section to a floppy for your
personal use but do not use this option to move files
between file section directories for users. If you
wish to move the file to another file section directory
use the File Move commands, which will also move the
file's information. The Kopy command is available only
to SysOps.
View the File
If a viewer is available you can view the file. This
may help in deciding the description of file, whether
or not to delete the file or grant uploader credit.
Text File List
This command creates an FD<date>.LOG file listing the files in
the directories that you select. Each entry includes filename,
file size, file date, file description, uploader's user number,
times downloaded, visible designation, private designation, and
password.
Because some of the information contained in this listing is
private, do not use this file as a downloadable list of files for
the users. However, this file could be edited to serve that
purpose. A DCI utility, DCIFUTIL, will create a list of files
and add GIF file information to the file descriptions.
Whole File List
This command will display all file information in specified
directories to the screen including information on removed and
deleted files.
DOS Dir
If you are online locally this command will display the actual
DOS directory listing to your screen.
File Move
This command will move a file from one file section directory to
another. Use this option if you only wish to move a few files.
For moving many files, such as when you decide to clear the
Upload Directory, Mass Move is preferred as it will move the
files automatically once you have specified which files to move.
When a file marked as Restricted is moved to another directory,
it is toggled to Not Restricted and the Designated Recipient's
name is removed.
98
Mass Move
This command will move many files at once after you have set it
up.
First select the files that you wish to move. At the "Select
files to move from directory" prompt enter the file section
directory number containing the files that you wish to move.
You will then be shown all the filenames followed by their
NewDirectory number (ND:) and prompted (Y/[N]/A/I/B/D):
Y)es, change NewDirectory
N)o, don't change it, next file
A)bort file selection procedure
I)nformation on file, please
B)ackup to the previous file
D)elete the file
K)opy file
The NewDirectory is the number of the file directory that the
file will be moved to. When a file is uploaded to the SysOp,
Privately, or as an Include Message, the NewDirectory designation
is the current directory number. Other files are given the
Newdirectory designation that the uploader selects. If you do
not want a file to be moved, its NewDirectory should be the
directory number of the directory it is in.
Once you are satisfied that all the NewDirectory designations are
correct, you can Select D)irectories and indicate which file
section directories you wish to move files from. You will be
shown any selected directories and prompted to add any others.
You may add several or only one.
You do not have to move the files at this time, the NewDirectory
information is retained in the records. If you are ready to move
the files, select M)ove files now. Any moved files are recorded
as DELETED in their original data files. It is best to Purge or
Sort (if you want the remaining files listed alphabetically)
directories that have had files moved from them.
Protocols (See PROTOCOLS)
Purge Files
Removes information on deleted files from the data files. This
will speed the execution of other commands. Always use this
command or Sort after a Mass Move. Purge does not alphabetize
the data file records.*
Rearrange Directories
Rearranges the directory listing. You must select the
directories that you wish to rearrange by using D)irInfo and
changing the directory number.
99
Sort Files
Removes information of deleted files and sorts the data file
alphabetically by file name. It is best to leave the Upload
Directory files in chronological order (Purge).*
Virus and Integrity Checking
If the SYS: CONF, Transfer Section, Upload Virus Check is set to
YES, the board will run VCHECK.BAT after a file is uploaded.
If the SYS: CONF, Transfer Section, Upload Integrity Check is set
to YES, the board will run ICHECK.BAT after a file is uploaded.
You may use any appropriate DOS utility you choose to accomplish
these checks. However, the utility must accept the filename on
the command line and must return a zero exit code if the file
passes the check and a non-zero exit code if it fails.
Sample batch files are included. DCI will execute the batch
files as <BATCHFILE> <path/filename> <comport>. Pass the file
name to the utility program using the %1 parameter. The comport
can be passed as %2.
* Attempting to Purge or Sort a directory containing more than
500 files will result in a message advising the removal (by
deletion or moving) of files.
100
DCI and DESQVIEW(tm)
DESQview(tm) is Quarterdeck's multitasking shell for MS-DOS.
With it you can run several programs at one time, switching
between them at will. DCI will run well under DESQview(tm),
allowing you to run the BBS while doing other work on your
computer at the same time. It is even possible to use another
telecommunications program at the same time as DCI on another
serial port. The best performance under DESQview(tm) will be
found on a 386 or 486 computer with at least 2 megabytes of
memory, although you will be able to use a 286 computer and/or
less memory with some limitations.
When run under DESQview(tm), DCI will release the CPU when there
is no activity on the board. This is done to help improve the
overall performance of the system. When idle, DCI will usually
use only one timer tick before releasing the processor for other
programs. During a user's session DCI will use more CPU time but
will still give up some of its timer ticks when waiting for input
from the caller.
DESQview(tm) allows you to set the maximum number of timer ticks
the foreground and background processes will receive before
switching to another program. There is no firm rule as to how
these should be set, as the optimum setting varies depending on
the speed of the computer and what other programs are running
besides DCI. The only way to discover the optimum setting for
your system is by experimentation.
It is important to tell DESQview(tm) not to swap DCI out if
memory runs low. If an interrupt comes in while the DCI has been
swapped to disk or EMS it is possible that characters could be
lost or that the system could crash. This can be prevented by
setting the .DVP file for DCI to indicate that a comm port is in
use.
A file is available on Nordevald Software's BBS, DCIDVKIT.ZIP,
which contains the .DVP, batch files, and related utilities for
running DCI under DESQview(tm).
101
DISPLAY FILES
Display files are text files with sections marked by special
dividing lines that tell DCI which part of the file to display to
the user. Using this method, the system MNU files contain
numerous small messages within just a few files making it easier
to maintain the files and using less room on the disk to store
them.
The display files that can be attached to bases and file
directories contain sections that are displayed based on the
current user's graphics and color settings.
The MNU files are required for DCI to operate properly, although
sections of some of these files are optional. These files
display important information to the users at various points in
the system. This information is contained in these files so that
you may customize it according to the needs of your system.
Display files linked to message bases and file directories are
optional.
Display files may also contain special codes, which are listed
below.
Format
The dividing lines in a display file contain a code that the
system needs to find the proper location in the file before
displaying it to the user. The dividing lines must begin with
two asterisks followed by DCI. You may add your own comments on
the line as text on a dividing line is not displayed.
**DCI this is a sample dividing line for a display file.
The message base display files, file directory display files, and
any Include Messages that contain ANSI graphics must be divided
into sections separated by display lines to avoid displaying
"garbage" to users whose terminals cannot properly interpret ANSI
codes and characters.
This is the format for a display file (system MNU files are
covered in more detail later):
**DCI ANSI & color display
**DCI ANSI display - no color codes
**DCI ASCII display
The text after the first dividing line and before the second will
be displayed to users who have color and graphics on. The second
display will be shown to users who have color off and graphics
on. The third display will be shown to users who have color and
graphics turned off.
102
Some ANSI cursor commands and clear screen commands will
interfere with the status line on the bottom of the local screen.
You do not need to include the ANSI clear screen command as the
system will automatically clear the screen before displaying
sections from most display files.
Special Codes
You may also include codes in the files to display specific
information. The codes are comprised of two forward slashes (//)
and a letter:
C - number of days from today to date. This code letter
must be followed by a date in the MM/DD/YYYY format.
C- - number of days since date. This code letter must be
followed by a date in the MM/DD/YYYY format.
D - current date in the format MM/DD/YYYY
H - hangup modem
K - waits for a key to be pressed. Input is not displayed
M - displays "Press any key" only if the user has menus
turned on (for use in Base Display Files instead of //W)
N - number of times user has called
S - clears the screen
Note: this is not necessary at the beginning of message
base display files as the system clears the screen by
default.
SL - security level (see below)
T - current time in the format HH:MM am/pm
U - user's system name
V - software version number
W - will display "Press any key " on the screen and wait for
input. The input will not be displayed.
X - disable *MORE* prompts while the remainder of the file
is displayed.
For instance, to create a screen that contains "Only # more days
until Christmas", you would enter: Only //C12/25/1990 more days
until Christmas. The code //C-12/25/1990 would display the
number of days since 12/25/1990.
To use the Security Level Code, it must be followed by the low
and the high security level designations:
//SL<low security level>;<high security level>
DEFAULTS: Low Security Level = 0, High Security Level = 255
This Code tells DCI to display the following text to users who
have security levels equal to or greater than the Low Security
Level and equal to or less than the High Security Level.
Remains in effect until either the end of the file or another
//SL#;# code.
Use with extreme caution in REGISTER.MNU. Registering users have
a default access level equal to a verified registered user until
103
the point of callback. It is best not to use this code in
REGISTER.MNU.
Required MNU Files:
BULLETIN.MNU main bulletins
ETC.MNU file upload, file participation, adding a base
info, unanswered chat request
FILEBULL.MNU file bulletins
HELP.MNU command help
INFOFILE.MNU File Menu Information Section files
INFOMAIN.MNU Main Menu Information Section files
LOGONOFF.MNU logon and logoff screens
MENU.MNU main and file menus
REGISTER.MNU new user registration prompts and info
Each of these files is explained in more detail, including a
listing of their formats, below. The sections in each of these
files are in a specific order. Do not change them. If you do
not wish to display a message in a particular section delete any
text in that section but do not delete the dividing lines.
BULLETIN.MNU
**DCI permanent main bulletin
**DCI one-read only bulletin
The permanent bulletin is displayed every time a user logs on.
If you do not wish to display a permanent bulletin leave the
section between the two dividing lines blank.
The one-read bulletin is displayed to each user only once. It is
also displayed at logon. When you change the one-read bulletin,
reset the users' main bulletin pointers (SYSOP: SYSTEM).
Both bulletins can be read again by selecting B on either of the
I)nformation menus.
ETC.MNU
**DCI Upload directory prompt
**DCI File participation text
**DCI Add base info
**DCI Chat request feedback
When a user is going to upload a file, the system prompts the
user to indicate which area the file should be placed in. The
upload directory text is displayed above this directory listing.
The text display is optional, but may be used to clarify the
types of files you want in certain directories.
The file participation text is displayed after the Upload,
Download, and Participation information in File Section S)tats.
This is also optional.
104
Add Base info is displayed before the base name prompt when a
user is adding a base. It is not displayed to SysOps. This is
also optional.
Chat request feedback text is displayed before the feedback
prompt when a user's chat page is not answered.
FILEBULL.MNU
**DCI permanent bulletin
**DCI one-read only bulletin
These bulletins are similar to the main bulletins stored in
BULLETIN.MNU. They are displayed to the user when entering the
file section. If you change the one-read only bulletin reset the
users' File bulletin pointers (SYSOP: SYSTEM). These are also
optional.
HELP.MNU
**DCI main menu help file
**DCI file menu help
**DCI Non-ANSI editor commands help
The Main Menu help file is displayed when a user enters H, or ?
if his menus are on, at the Main Menu. This file is necessary.
You may alter this file if you wish, but please try to keep it as
brief as possible with more detailed help in the I)nformation
files.
The File Menu help is displayed when a user enters H, or ? if his
menus are on, at the File Menu. This file is also necessary.
The Non-ANSI editor commands help file is displayed when a user
using the Non-ANSI editor enters /H in a message. This file,
too, is necessary.
INFOFILE.MNU
This MNU file can hold up to eight separate display sections for
the File Section I)nformation area of the board. These files may
be modified at any time (see INFORMATION).
INFOMAIN.MNU
This MNU file is similar to the INFOFILE.MNU and displays files
for the Main Menu I)nformation area. The initial board setup
includes six of these files defined, leaving the first two for
you to define as you wish. You may change these at any time by
changing the text within the MNU file and modifying the Titles
displayed (see INFORMATION).
105
LOGONOFF.MNU
**DCI LOGON/OFF #1 initial greeting BEFORE logon prompt!
**DCI LOGON/OFF #2 welcome ansi color
**DCI LOGON/OFF #3 welcome ansi no color
**DCI LOGON/OFF #4 welcome no ansi no color
**DCI LOGON/OFF #5 welcome 40 columns
**DCI LOGON/OFF #6 goodbye 80 color
**DCI LOGON/OFF #7 goodbye 80 ansi, no color
**DCI LOGON/OFF #8 goodbye 80 ascii, no color
**DCI LOGON/OFF #9 goodbye 40 columns
**DCI LOGON/OFF #10 storm
This file contains the text displayed when users logon and log
off the board. These are all optional but it is highly
recommended that you define several of them to personalize your
system.
The initial greeting is displayed before the logon prompt. Any
display in this section should be ASCII only, no ANSI codes, as
the user's color and graphics capabilities are not yet known.
The welcome screens are displayed as soon as the user enters his
password and is given access to the system. Design each welcome
screen to meet the various display capabilities.
The goodbye screens are displayed after the feedback option at
logoff.
Pressing Control-HOME (the storm key) on the local keyboard will
display the storm section and then log the user off the system.
It can be used as a storm warning so that the system can be taken
down in inclement weather or perhaps as a maintenance message to
free the board for a local logon.
MENU.MNU
**DCI MENU #1 main menu 80 color
**DCI MENU #2 main menu 80 ansi, no color
**DCI MENU #3 main menu 80 ascii
**DCI MENU #4 main menu 40
**DCI MENU #5 file menu 80 color
**DCI MENU #6 file menu 80 ansi no color
**DCI MENU #7 file menu 80 ascii
**DCI MENU #8 file menu 40 columns
This file holds the main and file menus with different displays
based on the user's graphics and color capabilities and screen
width. These are all absolutely necessary.
106
You may customize any of the sections in this file but take
special care to stay within the defined ASCII/ANSI and screen
width formats. Do not include ANSI clear screen commands in
these files as the system takes care of that.
Color menus can contain ANSI color and cursor positioning codes
and ASCII characters above 127 (IBM graphics). Ansi, No Color
menus can contain all of the above except color codes. ASCII
menus should be limited to alphanumeric characters only (ASCII 32
- 126).
REGISTER.MNU
**DCI REGISTER #1 system welcome
**DCI REGISTER #2 handle prompt
**DCI REGISTER #3 real name prompt
**DCI REGISTER #4 terms
**DCI REGISTER #5 callback screen
**DCI REGISTER #6 modem help
**DCI REGISTER #7 reentry -- actually a buffer
**DCI REGISTER #8 final text and seen by SysOp-added new users
**DCI REGISTER #9 long distance not allowed caller information
**DCI REGISTER #10 long distance allowed caller information
**DCI REGISTER #11 registration closed notice
**DCI REGISTER #12 registration closed, pre-feedback request
The text in this file is very closely integrated with the
registration process of DCI. Alter this file with extreme
caution.
The System Welcome is displayed when a user first enters the
registration procedure. A simple "Welcome to <bbs name>" is
adequate.
The handle prompt text explains to the user about using handles
on the system and is displayed just before the handle prompt. If
System Handles are set to 0 this will not be displayed.
The real name text is displayed just before the prompt for the
user's real name and location.
The terms text is displayed just before the prompt "Continue with
registration (y/n)?". This is very important if you expect users
to abide by certain policies which you enforce on your system.
If the user answers no at this prompt the registration process
will be aborted and the user will be logged off.
The callback text briefly explains to the user what to expect of
the callback procedure and what to do if callback is not
completed. Please include "Please disable your host mode" in
this text as this is the primary reason that users who do manage
to connect on callback fail to complete the procedure.
107
The modem help text is displayed if the user requests more
information. This should include more detailed help in how to
answer incoming calls. Going into great detail in this
explanation will probably only confuse most users.
The reentry text serves primarily as a buffer when the user first
connects with the system. Do not put any important information
on the first few lines in this section because the user may not
have initially made a clean connection, cutting off part of the
display.
The final text is displayed to the user right before s/he gains
entry into the board. It is also displayed to new users that the
SysOp has added on their first call.
The next section is displayed to long distance callers when the
board is not allowing them access. Include in this text any
requests for information you would like them to leave in
feedback.
The next section is displayed to long distance callers when the
board is allowing them access. If you are allowing these callers
to be called back explain that they will only have one try and
what to do if it fails. If you aren't allowing callback this is
the place to explain any restricted access and any additional
requirements you might have before giving them full access.
The Registration Closed Notice is displayed to registering users
when the system is not accepting new users. The Registration
Closed Pre-Feedback Request is displayed right before the
feedback prompt when the system is closed. If you wish to
restrict access to those who "apply" this is the place to put the
application.
AltKey Files
AltKey files are files stored in the \MNU directory. These files
are displayed to the user when an Alt-<number> key is pressed on
the local keyboard. For instance, to display a file when Alt-1
is pressed, create a file following the display file format and
name it ALTKEY.1. You may have up to nine AltKey files.
A very considerate use of an altkey file is one that tells the
user that the SysOp would like to chat and asks the user, if it
is convenient, to page him before logging off.
108
DROP TO DOS
The SysOp may shell to DOS from the local keyboard by entering
Alt-J from any prompt in the system. DCI remembers what
directory the board was in when you dropped to DOS and will
change directories for you when you return to the board. To
return to the board type EXIT at the DOS prompt.
Several internal DOS commands are not re-entrant. That is, they
will upset the memory of your system and should not be run when
you are in a shell of another program. Do not enter the Time or
Date command when you Drop to DOS; use the SYSOP: SYSTEM Date and
Time commands instead or you will be forced to reboot.
If you try to run DCI from within this shell, you will see a
message indicating that DCI is already loaded unless DCI was run
with the /NOCHECK switch.
To drop to DOS from remote, you may use the DOSSHELL.BAT file
included in the DCI package. Set this up as a SysOp door with
Remote Only status and %P as the parameter (to tell the batch
file which comm port to use). This batch file uses the DOS CTTY
command. Please note that should you drop carrier while in this
shell, the system will have to be rebooted as there is no carrier
checking and all input and output have been redirected to the
comm port. Also, not all programs will work correctly using this
type of redirection. You may encounter instances when the
computer is sending information to the port too quickly and get
an error message. After a few seconds, Retry should allow you to
continue.
109
EDITORS
DCI provides a Non-ANSI and a full screen ANSI editor. Both
editors have numerous editing commands and help screens. The
Non-ANSI editor can be used by any user regardless of color and
graphics capabilities. The ANSI editor, however, requires that
the user's terminal fully support ANSI sequences. Several of the
most popular communications programs do support ANSI and others
have terminal emulations (VT-100, VT-102) that do. From the
local keyboard either editor may be used.
The ANSI editor supports cursor movement and accepts Wordstar
commands. It operates in either Insert or Overtype mode. It is
limited to 200 lines of text while the Non-ANSI editor, a line
editor, will accept messages of greater length depending on
available system memory.
Editor selection is from the Configuration Menu. Only users who
have graphics and color turned on will see the Editor option on
this menu. If a user has previously selected the ANSI editor and
then turns off either color or graphics, the editor selection
will be changed to the Non-ANSI editor. Users who select the
ANSI editor may also select the background and text colors for
the editor.
Both editors support the inclusion of Include Files and DCI color
codes and accept ASCII uploads.
In both editors, users will be alerted when their time remaining
is 5 minutes or less. When they have run out of time, they will
be given the option of aborting or saving the message.
When mass mail is available (SYS: CONF settings and a private
message is being posted), the Mass Mail option will be available
to the user.
ASCII Uploads
ASCII uploads of text are supported by both editors. A user who
is not familiar with this practice may assume that the editor has
garbled the format of the text. This is usually not the case and
Listing Formatted in the Non-ANSI editor or Redrawing the screen
in the ANSI editor will show the message as it will appear saved.
Color Codes
The following color codes are supported within messages:
BR - brown LM - light magenta
CH - charcoal LR - light red
CY - cyan MA - magenta
GR - green MB - medium blue
GY - gray RE - red
LB - light blue/cyan YE - yellow
LG - light green WH - white
110
In addition, \NO sets the color to "Normal", the defined base
text color. A back slash (\) must precede the color code for the
system to interpret it correctly. The color codes can be entered
as either upper or lower case.
In the non-ANSI editor, if a user has color selected the color
codes will be displayed across the top of the initial editor
screen. They can be redisplayed by using the /CC command. In
the ANSI editor, the command ^QC will display the codes across
the top line of the editor screen.
The entry \REThis is \BLblue\YE! would be displayed as "This is "
in red, "blue" in blue, and "!" in yellow.
If the user is in the Non-ANSI editor the command /LF will
display the message in color. In the ANSI editor, the command is
^QR.
When the message is read, only users with color selected will see
the colors.
Graphics Characters
Higher ASCII characters (IBM graphics) are allowed in both
editors. If the user entering the message has graphics turned
off, the Editor Graphics Mode will be OFF, not allowing these
characters to be entered. If a user with graphics turned on
enters an editor the Editor Graphics Mode will be ON.
The Editor Graphics Mode can be changed from within the editor
(/CH or /CG in the Non-ANSI Editor, ^QH in the ANSI editor).
This allows a user who does not want graphics to be displayed to
enter a message containing graphics, or a user who has graphics
to combat hits of line noise.
When a user with graphics turned off reads a message containing
graphics, the graphics characters will be translated to
alphanumeric characters.
Several characters are not allowed as they are used as control
codes in telecommunications or have special meaning for DCI.
These characters include those below ASCII 32 (the control
characters) and ASCII 255.
Higher ASCII characters can be entered by holding down the ALT
key while typing in the number of the character. Holding down
ALT and pressing the 1,5,5 keys will produce a cent sign.
Mass Save
Mass Save allows a user to send copies of a message to multiple
users. It is supported in both editors. After the first message
is saved, the user will be prompted to enter the name of the next
user to send the message to. Pressing <enter> at this prompt
ends the procedure.
111
Mass Save is only allowed when the message is Private. The SysOp
sets the security level necessary to access this feature in SYS:
CONFIG.
Include Files
The commands %%<filename>, to include a text file, and
%%<filename>%%, to include a display file, are available in both
editors. The file must be in the board's Include Directory in
the file section unless the message is posted by the SysOp. The
SysOp may include files in messages that are not located in the
Include Directory, however, the fullpath name must be included in
the filename designation (%%path\filename%%).
If the user enters a code to include a text file in the message,
the commands /LF and ^QC in the Non-ANSI and ANSI editors
respectively, will display the message and the contents of the
file. See INCLUDE FILES for more details on their format.
Message Quoting
Message Quoting is a way of including a few lines of text of the
message being replied to in the current message. This helps to
maintain threads of messages particularly in an active base. Any
lines quoted will begin with ">> " to indicate that they are
quotes.
The Quote Message command in each editor (/QM in the Non-ANSI;
^QM in the ANSI editor) will invoke a prompt that will allow the
user to Display and/or Quote the message he is replying to.
Display (D) will list the original message with line numbers.
SysOps can use this as a limited scroll back buffer when online
from the local keyboard. Display can also be invoked by entering
Dn;x, where n is the first line and x is the last line to
display.
The Quote command (Q) must be followed by an indication of the
lines in the message to quote. To quote one line, enter Qn where
n is the line number; to Quote several lines, enter Qn;x where n
is the first line and x is the last line number; to quote the
entire message, enter QA (quote all). With the exception of the
Quote All option, only 10 lines may be quoted at one time;
adjustments will be made to the last line number if it exceeds
this limit. To prevent nested quotes, quoted lines in the
original message may not be quoted a second time.
ANSI Editor
The ANSI editor is a full screen text editor. Unlike the
Non-ANSI editor which formats messages after they are saved, the
ANSI editor saves messages exactly as they appear on the editing
screen. This facilitates including columns and lists within a
112
message. Most of the editing is done by using the cursor keys
and the standard WordStar command set.
As a full screen text editor some liberties have been taken to
improve performance and lessen delays when displaying over the
modem. Most obvious is that the editor does not scroll down one
line at a time as the user is entering text. When the display
changes to the next screen several lines above the current line
are included. Updating screens requires more time and hence is
minimalized.
This Editor has two Help Screens. The first is invoked by
pressing ESC. The second can be invoked from the first by
entering M for More. Any other key will remove the help screen
and the user can continue editing the message.
The editing commands are invoked by keys that are used by some
communications programs for their own commands (such as PgUp and
PgDn). These will function as expected when entered from the
local keyboard but can also be invoked by other commands. Users
may find it easier to reassign some of the keys in their
communications program (such as the left arrow key) to be able to
use them rather than remember the Control-KEY combinations. The
Help Screens display all keys and key combinations to invoke the
commands.
To enter a Control-KEY combination, hold down the CTRL key and
type the KEY. To type ^S, hold down CTRL and type S. To type
^KB, hold down CTRL, type K, release CTRL, type B.
Insert/Overwrite Mode
The editor defaults to Insert Mode. When Insert Mode is active
any text to the right of the cursor will be moved to the right as
more text is entered or moved to the next line if a carriage
return is entered. In Overwrite mode, existing text is
overwritten and a carriage return moves the cursor to the
beginning of the next line. The Mode is toggled by the Insert
key.
Movement Commands
<ENTER>
The Enter key inserts a carriage return. When the cursor is at
the end of a line the cursor moves to the beginning of the next
line. If the cursor is to the left of the end of the line any
text to the right of the cursor is moved down to the next line if
the Insert Mode is on. In Overwrite Mode, the cursor simply
moves to the beginning of the next line.
<TAB>
The Tab key will enter 5 spaces into the text of the message, or
advance the text 5 spaces if Insert Mode is active.
113
Beginning of Line: Home, ^QB
Move the cursor to the beginning of the current line.
End of Line: End, ^QE
Move the cursor to the end of text on the current line.
Up one Line: Up Arrow, ^E
Move the cursor up one line. If the cursor is on the top line of
a screen other than the first, the display will move up to the
previous screen.
Down one Line: Down Arrow, ^X
Move the cursor down one line. If the cursor is on the last line
of the current screen but not the last line of text, the display
will move down to the next screen.
Left one Character: Left Arrow, ^S
Move the cursor one character to the left. If the cursor is at
the left margin, move to the end of the previous line.
Right one Character: Right Arrow, ^D
Move the cursor one character to the right. If the cursor is at
the right margin, move to the beginning of the next line.
Beginning of Left Word: ^Left Arrow, ^A
Move the cursor to the beginning of the word to the left. If the
cursor is at the left margin and the current line is not the
first line of text, the cursor will move up to the end of the
previous line.
Beginning of Right Word: ^Right Arrow, ^F
Move the cursor to the beginning of the word to the right. If
the cursor is at the right margin and the current line is not the
last line of text, the cursor will move down to the beginning of
the next line.
Previous Screen: PgUp, ^W
If the current screen does not contain the first line of text,
the previous screen will be displayed.
Next Screen: PgDn, ^C
If the current screen does not contain the last line of text, the
next screen will be displayed.
Top of Message: ^PgUp, ^PU
Move to the beginning of the message.
End of Message: ^PgDn, ^PD
Move to the end of the message.
114
Editing Commands
Save/Exit: ^Z
This command will display a prompt at the top of the screen
allowing the user to enter:
S - save the message.
M - mass save (if allowed).
D - delete message options:
A)bort msg - do not save the message, exit editor.
C)lear msg - clear the editor and start over.
R)eturn - return to the editor, no changes.
Save: F6
From the local keyboard, pressing F6 will save the message
without any further prompting.
Toggle Mode: INS, ^V
Toggle Insert/Overwrite mode.
Delete Character: DEL, ^G
Unlike backspace which replaces the character with a space,
delete removes the character and moves text to the right back one
space.
Delete Line: ^Y
The line under the cursor is deleted, and any text below it is
moved up one line.
Reformat Paragraph: ^B
The first blank line either under or above the cursor and the
next blank line below the cursor define the paragraph. All text
in this region is reformatted, moving text up to previous lines
if possible. This command will reformat quoted lines maintaining
the quote format.
Delete Right Word: ^T
The next word or series of spaces will be deleted.
Replace String: ^QA
The user will be prompted for the string to search for and then
prompted for the replacement string and the search options:
Q - quit. Abort search and replace.
Where:
G - global.
Replace all instances of the search string from
the beginning of the message to the end.
L - local.
Replace all instances of the search string within
a defined block of text.
B - backward.
Replace all instances of the search string from
the current line to the beginning of the message.
Default: Replace from current line to end of message.
115
Case Sensitivity:
I - ignore case.
Default: Replace only instances of the search string that
match exactly.
Word Boundaries:
W - replace whole words only.
Default: Replace all instances of the search string.
Mark Beginning of Block: ^KB
The block functions only support designating entire lines, not
words, as block boundaries. A highlighted block character will
appear in the right margin.
Mark End of Block: ^KK
A highlighted block character will appear in the right margin.
Move Block: ^KV
The marked block will be moved to the current line and the screen
updated.
Delete Block: ^KY
The block of text will be deleted and the screen updated.
Miscellaneous Commands
Redraw Screen: ^R
In case of line noise, the user can redraw the current screen.
Redraw Screen in Color: ^QR
If the user has added color or include file codes to the text of
his message, this will allow him to view the message with the
codes interpreted.
Color Code Display: ^QC
The color codes will be drawn across the top line of the screen.
Change Header/Graphics: ^QH
This allows the user to change his Graphics setting and the
information in the header of the message depending on the message
display format of the base he is posting in. The user will be
prompted for the specific command. These can also be entered
directly:
F - Change From
If the message header indicates who the message is from
and the user has more than one identity, he may change
the From entry.
G - Change Graphics
This will toggle whether or not graphics characters are
allowed in the message.
S - Change Subject
If the message display format includes a Subject or
Action, the user will be able to change this. When in
116
the debate format, the user's position on the topic may
also be changed.
Quote Message: ^QM
If the user is replying to a message, he will have the option of
including lines from the original message in the text of his
message.
Quote Whole Message: ^QW
If the user is replying to a message, this will include the
entire text of that message into the current message.
Non-ANSI Editor Commands
All editor commands must be preceded by a forward slash (/). The
commands are structured so that a user who is not familiar with
the editor can enter /E or /? to display a menu of available
commands and be prompted to enter the necessary information.
Commands must be entered as the first characters on the line. If
the user enters an incomplete command, the editor prompt will
appear.
The following commands are available:
/E Editor Commands
/CC Color Commands /L List Message Unformatted
/CH Change Header /LF List Message Formatted
/CM Clear Message /QM Quote Message
/DL Delete Line /RL Replace Line
/DM Delete Message /RS Replace String
/H More Help /S Save Message
/IL Insert Line /SM Mass Save
Editor Command Menu: /E, /?
This option displays the editor commands and invokes the editor
prompt, which reassures users until they become more comfortable
with using the editing commands directly.
List Color Codes: /CC
The color codes will be displayed. If the user can support
color, the codes will be shown in their respective colors.
Change Header/Graphics: /CH
The prompt line includes Change From and Subject, the Graphics
Toggle, and the List Color Codes and Clear Message commands.
Clear Message: /CM
This will clear all the text that had been entered, allowing the
user to start over from the first line.
Delete Line: /DL
This command will remove a line from the message. The command
can be entered as /DL;n where n is the number of the line to
delete. If no line number is entered, the user will be prompted
for more information.
117
Delete Message: /DM
After confirmation, this command deletes the message and exits
the editor.
Help (Extended): /H
This will display the Non-ANSI Editor Command section of
HELP.MNU.
Insert Line: /IL
This command will insert a line into the message. The command
can be entered as /IL;n where n is the line number of the new
line. If no line number is entered the user will be prompted for
it. Entering 3 will insert a new line before the current line 3.
The user will then be prompted to enter the text of the new line.
Pressing <ENTER> will enter a blank line.
List Message Unformatted: /L
This command will list the message with line numbers, showing
color codes and include file codes, with no word wrap. This is
helpful when editing. If the command is entered without line
numbers, the entire message will be displayed. The command can
also be entered with line numbers, /Ln;x, where n is the first
line to list and x is the last line. This display can be aborted
by pressing the space bar.
List Message Formatted: /LF
This will list the message as it will appear after it is saved.
Line numbers are not included, all codes are interpreted (color
will be displayed, as will the contents of include files), and
word wrap is in effect. If the command is entered without line
numbers, the entire message will be displayed. The command can
also be entered with line numbers: /Ln;x, where n is the first
line to list and x is the last line. This display can be aborted
by pressing the space bar.
Quote Message: /QM
If the user is replying to a message, this command allows the
user to indicate which lines from the original message, if any,
he would like to quote within his message.
Replace Line: /RL
This command is used to replace an entire line of text in the
message. The old line will be deleted and the user will be
prompted to enter the new line. The command can be entered as
/RL;n where n is the number of the line to replace.
Replace String: /RS
This command is used to replace a string of text up to 40
characters in length. The command can be entered as
/RS;n;oldtext;newtext, where n is the number of the line
containing the string to replace (or A for All lines), oldtext is
the string to replace, and new text is the string to replace it
with. If line number or string information is not included with
the command the user will be prompted to enter more information.
118
String replacement in this editor is case sensitive. If the user
wishes to replace all instances of "the" with "THE" in "The sun
is in the west", the new line would read "The sun is in THE
west". The first instance of "the" in the sentence is
capitalized and hence, does not match.
String Replacement does not span line boundaries. The search and
replace is done on a line by line basis. If the search string
begins on one line and ends on another, it will not be replaced.
The List Unformatted command (/L), will help in this case.
Save the message: /S
This command saves the message and exits the editor.
Mass Save: /SM
This command will save the message and allow the user to send
copies to other users.
119
EMS USAGE
By default, when DCI is first run, it will attempt to use EMS
memory. If you do not have EMS memory or do not want DCI to use
it, run DCI with the /NOEMS switch on the command line. Using
the /NoEMS switch will also slightly speed up the time it takes
for DCI to load and begin running. One of the following messages
will display to tell you the status of EMS usage:
Fatal Error Messages
Overlay: I/O error -- DCI.OVR damaged
The DCI.OVR file has been damaged and cannot be read from the
disk. Rename DCI.OVR to DCI.BAD and place your backup copy of
DCI.OVR in the DCI directory.
Overlay: Not enough memory
There is not enough available memory for the DCI overlays to be
loaded when needed. Uninstall any TSR's and try again.
Information Messages
EMS driver not installed
Your system does not have an EMS driver installed. DCI will use
conventional memory only.
EMS override
DCI was run with the /NOEMS switch and is not even checking for
the presence of EMS memory.
Not enough EMS memory
EMS memory was found but there is not enough for DCI to make use
of it. Conventional memory will be used.
Using EMS memory
DCI will make use of the available EMS memory.
120
EVENTS
Events are external programs and internal procedures that the
system executes at the specific times and dates that you define.
Tasks that must be done repeatedly at regular intervals are best
suited to be run as events, cutting down on system maintenance
time.
For instance, you need to periodically purge the system Call Log
because it gets too large. Rather than having to remember to do
this manually every few days, you can run it as an event using
the system's internal purge command. You can also run an event
that would call a batch file that backs up all the system files.
Not only do events free you from doing the tasks, they also free
you from remembering to do them.
DCI has internal event procedures that will purge log files, move
files from one directory to another in the file section, purge
and sort file directories, delete received E-Mail, delete
messages, delete users, and take the board down to run special
events that can not be run from within the board.
Each event has a window, a time span, during which it should
execute. You define this window by setting the begin and until
times of the event. Another factor is whether or not the event
slides within this window. If an event is set to slide, the
system will make sure that it executes after the begin time and
before the end time. If it is not set to slide, the system will
execute it at the begin time, if possible, but no later than the
end time.
The system considers the time the event must execute as being the
end time of a sliding event or the begin time of a non-sliding
event. The system continually monitors the time, comparing it to
the time the event must run. If a user logs on and the event
time falls within the user's time limit, the user will be
notified that an event is scheduled in # minutes, and asked if he
wishes to continue logging on. If the user does continue, and
his time for the call is more than the number of minutes until
the event, his time for the call will be adjusted so that he must
log off before the event time, and his account will be credited
for the time he lost on the call.
If a user logs on and there is less than six minutes until an
event must run, or if a new user wishes to register and there is
less than nine minutes until an event must run, the system will
notify the user that there is not enough time and ask him to
please call back, logging the user off. For this reason, it is
best to run non-sliding events during times when the board
usually isn't busy, or run sliding events in large time windows.
With a sliding event, and a time window of two hours, most events
execute within the first hour without the users being
inconvenienced or even aware that an event was scheduled.
121
When an event executes, the system first takes the modem
off-hook, and then displays an "Event Executing" message on a
highlighted status bar. After the event runs, the result code of
the event is written to the event record, and a notation is made
in the Activity Log. The next date of the event is calculated,
and the system moves the next scheduled event into the queue.
The next scheduled event is also noted in the Log. The modem is
then put back onhook and the system waits for the next caller.
If the system is down when an event is set to execute, the event
won't run. If the system doesn't go up before the end time of
the event, the event will be cycled and the next event will move
to the beginning of the event queue. Similarly, if events are
turned off during the event window, they will be bypassed.
All active events that were unable to run will be updated and
notations will be made in the Activity Log.
When resetting events, the system determines the next event as
the first scheduled ACTIVE event on or after the current date.
If the event is scheduled for the current day, the end time must
not have passed. Inactive or Deleted events and events with due
dates in the past will be bypassed. Do not set up an event that
has an event window that spans midnight.
If a user is online when an event time is nearing, the SysOp
won't be able to increase the user's time from the status line.
An E will appear on the Status Line next to Time rather than the
up arrow. The SysOp should also be cautious of chatting during
an event window, as the end time of the event could pass.
When running DCI with a front door program, pending events will
be checked as DCI is recycling. Normally, DCI constantly
monitors events. However, with a front door, DCI will only be
checking events when a user has logged on. For this reason,
increase event windows to cover periods of non-activity. Also,
switch all non-sliding events to sliding.
Few events have the ability to harm the system, though caution
should be used with any events that change directories or access
the modem. If an event fails it is usually because there isn't
enough memory available to run the event or an internal failure
of the event program (often invalid parameters being passed).
Failures such as these do not harm the board and will be noted in
the event record and Activity Log with the result codes. A
result code of 0 means that the event executed successfully in
most cases. Not all programs return result codes, in which case
the result only reflects that DOS was successful in running the
program, not that the program ran correctly.
When first defining an event, it is best to set the event to run
within the next few minutes, or F)orce the event to execute, and
watch to make sure the event is set up correctly. Once you have
defined the event, set it to Active, make sure events are set to
ON, and then reset events. This moves the next event to the top
of the event queue.
122
Event Fields
The information that DCI needs for each event is listed below.
Event Name
This is the name you give the event. It can be up to 12
characters long and should be something that identifies for you
what the event does. The event name will be displayed on the
Waiting Screen when it is the next event to be executed. It will
also display on the status line when you press Alt-E.
Filename
This is the full filename to execute when the event runs. It
must be an EXE, COM, or BAT file.
Begin Time
The beginning time, in 24-hour format, of the event window.
Until Time
This is the ending time, in 24-hour format, of the event window.
Frequency
This is how often the event should run. After the event runs,
the system will update the date and the begin and until times
based on the frequency of the event.
DCI provides for the following frequencies:
Once the begin and until times and date are not
changed, status is changed to Inactive.
Twice per day the begin and until times are incremented by 12
twelve hours, date changes as necessary.
Daily date increments by one day.
Weekdays the date is adjusted so that the event runs only
Monday through Friday
Weekends the date is adjusted so that the event runs only
on Saturdays and Sundays.
Twice per week if date is odd, increments by 3 days; otherwise,
increments by 4 days.
Weekly date increments by seven days.
Twice per month date increments by fifteen days.
Monthly date increments by one month.
Twice per quarter date increments by one month and 15 days.
Quarterly date increments by three months.
Twice per year date increments by six months.
123
Yearly date increments by one year.
If an event is set to Once, after it executes it will be set to
Inactive so that it cannot run again. Use this frequency with
special events, such as deleting specific users, that should only
run once. When needed again, the event parameters can be changed
and it can be set to Active.
Slide
This is whether or not the event slides in the time window.
Parms
This is a string containing the parameters that the event needs
to run. DCI internal event parameters are described below, or
check the docs of external programs (see PARAMETERS).
Due Date
This is the date when the event should run next. If you press
<ENTER> the date will be set to the current system date.
Status
This should be set to Inactive if you have not completed the
event definition, or Active if you have. If Status remains
Deleted, the event definition will be overwritten when a new
event is added, or removed when the event file is purged.
Result
This is the result code returned after the event executes. It is
automatically set to 0 when you define an event.
Event Commands
Add
Use this command to define a new event. If an event definition
has been deleted, the new event will take its place in the
record, otherwise the new event will be added to the end of the
records.
When Adding a new event, you will have the option to C)opy an
existing event record. This is useful if you have two very
similar events that differ only in times or parameters. Make
sure you change the Event Name so that you can distinguish
between the two.
Force
This command tells the system to execute an event immediately.
You will be prompted for the number of the event to run. This is
useful when defining an event to make sure that it executes
properly. If you receive a result code of 8, there is not enough
memory for the event to run. The system is using more memory
while you are on line and the event may be able to run while the
system is waiting for a call. Try setting the event to execute
in the next few minutes, Reset events to move it into the queue
and then log off and wait until it runs to see if it can be
124
successfully executed.
List
Display an abbreviated listing of all defined events so you can
see at a glance if all are defined correctly. Here is a sample
listing:
# Event Filename S F Sl Begin Until RES Parm Date
1. Soff BACKUP.BAT A D Y 03:00 06:00 0 Defd 08-20-91
S - Status -- A)ctive, I)nactive, D)eleted
F - Frequency
Sl - Slide -- Y)es, N)o
RES - Result code
Soff is event number one. It is an Active event that runs daily.
It tells the system to execute BACKUP.BAT in a sliding window
from 3:00 am to 6:00 am on August 20, 1991. The parameters are
defined. The last time it ran it had a result code of 0
(success).
Modify
This command is used to change any of the record fields of an
existing event.
Next
This command displays the Next Event WITHOUT resetting the
events. This is useful if you have modified events but do not
wish to move the current event from the top of the event queue.
Purge
Remove all event definitions with a status of Deleted from the
event file. Use this option to keep the event file from becoming
unwieldy.
Reset
Move the next scheduled event to the top of the event queue.
Swap
Rearrange the order of the Event records.
Toggle
Turn events turns Events ON and OFF. If events are OFF, no
events will be executed. If no events are defined, set Events
OFF.
Internal Events
These are internal DCI functions that you can run as events.
When defining an internal event the Filename field tells the
system what to do. The format is /I #. The "/I" indicates that
the event is internal, and "#" is the number of the internal
event to execute from the following list:
125
1 Purge log file
parms = logfile name (e.g., ACTIVITY.LOG)
2 Mass Move files
parms = directorynumber (more than one directory number
can be specified, separate with semicolons for a maximum
parm length of 40 characters).
3 Sort file directories
parms = directorynumber (more than one directory number
can be specified, separate with semicolons for a maximum
parm length of 40 characters).
4 Purge file directories
parms = directorynumber (more than one directory number
can be specified, separate with semicolons for a maximum
parm length of 40 characters).
5 Delete received E-Mail
parms = firstmessage;lastmessage
or
parms = L#
In the second case, # is the number of messages to Leave
in email when deleting received mail.
6 Delete messages
parms = basenumber;firstmsg;lastmsg
7 Delete users
parms = usernumber (more than one usernumber can be
specified, separate with semicolons for a maximum parm
length of 80 characters).
For example, to purge the Call Log early every morning, define an
event as follows:
Filename: /I 1
Name: CallPurge
Status: Active
Frequency: D
Begin: 02:00
End: 05:00
Slide: Yes
Due Date: <today's>
Parms: CALL.LOG
Use caution when defining the parameters of these events as the
system will do exactly what you tell it to do.
When using Mass Move Files, Sort File Directories, or Purge File
Directories enter the directory numbers separated by a semicolon.
For instance, if you want to Sort Directories 2, 4, and 6, the
Parms should be entered as: 2;4;6.
126
To Delete Received E-Mail, all received messages between the two
message numbers you enter as parameters will be deleted. If you
wish to purge E-Mail from message 1 to message 400, enter 1;400
as parameters.
To Delete Messages, you must also indicate the base number. If
you wish to Delete Messages from 1 to 100 in base 2, and from 1
to 200 in base 4 enter 2;1;100;4;1;200 as parameters.
To Delete Users, enter the user numbers separated by semicolons.
The Internal Commands return three possible Result codes:
0: success
254: internal event parms error
255: event failed because time window was missed
Halt Events
The board can be taken down as an event by entering as the event
filename: /HALT <haltcode>. The halt code can be any number
between 1 and 65535.
If you need to run a large program as an event, or a program that
needs full control of the comm port, you can run the board in a
looping batch file that branches to the other program based on
the exit code the board halts with (the <haltcode> you define as
part of the event filename). The batch file should execute the
program and then put the board back up.
For instance, if you wanted to backup data files once a week you
might want to do this with a halt as the speed of compression
utilities is dependent on how much memory they have to work in.
If you define your event with the filename /HALT10, your DCI
batch file might look like this:
:RUNDCI
DCI /NOEMS
if errorlevel 11 goto RUNDCI
if errorlevel 10 goto BACKUP
goto RUNDCI
:BACKUP
pkzip DCIBACK *.dci
goto RUNDCI
This batch file loops repeatedly to the RUNDCI label. To exit
the batch file you must press Control-C.
127
EXTERNAL DCI UTILITIES
There are several external programs that are necessary for the
correct operation of the software. These files should always be
located in the DCI directory.
DCI?SORT.EXE
DCIHSORT.EXE, DCIFSORT.EXE, and DCIDSORT.EXE are the programs
that sort the indices, file directories, and door listings. With
these as external programs you can have larger record files than
you could if they were internal. Do not run these programs
yourself; DCI executes them when necessary.
DCIEXPRT.EXE
The DCI Export Message Utility is used from within DCI to create
text files of messages stored in DCI's data files. It must be
located in the main DCI directory so the system can find it when
called from either the Message Prompt or SYSOP:MSG menu.
If you wish to use it outside of DCI, you may by using the
following format:
Call with:
DCIEXPRT <basenumber> <beg msg> <full filename> [end msg] [H] [T]
basenumber - The number of the base to log the messages from.
beg msg - The first (or only) message to log.
full filename - The full filename of the log file to be created.
[end msg] - The last message to log, if not indicated, or set
to 0, it will default to the last message in the
base.
[H] - Header format:
U - UTI (default)
D - Abbreviated DCI headers
F - Full DCI headers
[T] - Threading (default = no threading)
Error Codes
301 : invalid base number
302 : cannot find BOARD.DCI -- not in path
303 : cannot find MSG.DCI
304 : invalid filename
305 : invalid starting message number
306 : cannot find PRIMARY.NDX
128
DCIFCNT.EXE
This program increments the download counter of files that have
been successfully downloaded.
FORMAT:
DCIFCNT [ /F ]
The /F parameter tells DCIFCNT to Find the directory that a file
has been moved to if it is not in the directory it was downloaded
from. This option takes slightly more time, but unless DCIFCNT
is searching through numerous large activity logs or you have a
very large file section, it won't take long at all.
DCIFCNT can be run from the DOS prompt or as an event. It is
best to run it as a daily event.
Event Setup
Event Name : < your choice >
Filename : DCIFCNT.EXE
Status : Active
Slide : Yes
Parameters : /F or < none >
Due Date : < today's >
Begin Time : < your choice >
End Time : < your choice >
Frequency : Daily ( suggested )
This utility only searchs Activity Logs that have been purged
(i.e., renamed ACMMDDYY.L??). Make sure you run DCIFCNT before
you delete the purged Activity Logs. If you purge logs as a
daily event, set the DCIFCNT event to run right after the purge
log event. Once DCIFCNT searchs a log, it will rename it to
*.D?? ( i.e., .LOG becomes .DOG ) and then you can safely remove
it from the /LOGS directory.
ACTIVITY & ERROR MESSAGES
Exit Codes
0 : Successful execution
2 : HALT: Cannot find BOARD.DCI
Run DCIFCNT from the Main DCI directory
3 : HALT: Cannot find ACTIVITY.LOG
Run DCIFCNT from the Main DCI directory
5 : HALT: Cannot open MAINFILE.DCI
Run DCIFCNT from the Main DCI directory
Check SYS: CONFIG Transfer Path to make sure it is
correct
129
Messages
DCI FileCount :
DCIFCNT.EXE was executed
Nothing to do!
Either no purged Activity Logs were found or the ones
that were searched contained no successful downloads.
Found: # Updated: #
The total number of successful download notations found
in the Activity Log and the number of downloads that
were updated in the file data records. Discrepancies
are noted in the next message and the following Warning.
Not Found : < path > < filename >
The file's information was not found in the data record
of the file directory that it was downloaded from. This
may be because the file has been moved or deleted.
Note: this message only appears when the /F parameter is
not used.
Not Found : < filename >
The file's information was not found in the data record
of any of the file directories. This may be because the
Activity Log information was inaccurate or the file is
no longer in a file section directory. Note: this
message only appears when the /F parameter is used.
WARNING
Files that have been deleted or renamed, will account for the
difference between the Number of Files Found and the Number of
Files Updated. If the directory has since been deleted, these
files will not be updated either.
DCIPATH.EXE
DCIPath is an external utility program that allows you to easily
view and change the DOS directory paths stored in the DCI data
files. If you change any paths, you must also move the
appropriate data files to the new location(s).
DCIPath also allows you to change the comm port settings and
Private Logon Password.
DCIPURGE.EXE
DCIPURGE.EXE removes deleted message information from the data
files, resets users' message pointers, and renumbers the
remaining messages. If there are a lot of messages in a base
this will increase the speed of accessing the data files.
130
It does have limits. It will not work if there are more than
30,000 messages in a base. If this is the case, your only
alternative is to delete the base and begin from scratch.
FORMAT: DCIPurge <base number>[, or -]<base number>
DCIPurge 2,5 = purge bases 2 & 5
DCIPurge 2-5 = purge bases 2, 3, 4, & 5
DCIPurge 2-5,8 = purge bases 2, 3, 4, 5, & 8
Running DCIPURGE as an event:
Filename: DCIPURGE.EXE
Parms: /E <base>[, or -]<base>
Halt code information:
0: success
1: invalid parameters
DCIUSER.EXE
DCIUSER.EXE creates a new USER.LOG when you purge the existing
User Log. The log contains information in the following format:
Firstname Lastname (System Name) DPhone VPhone DOB City, State
The date of birth field is YY-MM-DD for sorting purposes. To
sort the file, use the DOS Sort command and one of the following
/+n commands where n is:
1 : Firstname
25 : System name
49 : Data Phone
66 : Voice Phone
83 : Date of Birth
93 : City, ST
The DOS command SORT < USER.LOG /+83 > USER.AGE will produce a
file named USER.AGE in which the entries are sorted by the users'
date of birth. The width of the lines in the file vary from 90+
to as wide as 130 characters. Printing in compressed mode is
suggested.
DCIUSER may also be run from the command line:
FORMAT: DCIUSER [ /V ] [ /? ] [ filename ] [ /D ]
/V = show version information
/? = show help screen
[ filename ] = name of the user log to create
Default = \DCI\LOGS\USER.LOG
/D = include deleted account information (Default: no)
131
FATAL ERRORS
DCI will generate errors due to software and hardware failures.
When a fatal error occurs a message will display on the screen
and an entry, FATAL ERROR, will be made in the Activity Log
followed by an explanation.
File Errors
DCI cannot run if certain data files are not found when it begins
to run. If any of these files are missing, a FATAL ERROR will be
generated followed by the name of the file. This is usually due
to a failure to install the software (see INSTALLING DCI). If it
is not a failure to install, make sure you are trying to run DCI
from the DCI directory. If that is not the solution, replace the
questionable file with a recent backup copy and try again. If
the error persists, make sure you have disk space free on the
drive and that there are no hardware errors on the disk where the
file resides.
Hardware Errors
If there is a problem with your hardware and DCI encounters it
during its normal operation it will alert you to the problem by
generating a CRITICAL ERROR followed by a message. This can be
caused by bad sectors on your hard drive and similar "normal"
hardware maladies. Please consult your hardware manuals for
assistance in correcting these problems.
Software Errors
Should DCI crash it will generate a FATAL ERROR followed by a
code. Please report this to Nordevald Software IMMEDIATELY,
either by logging on the Home Board or dropping a postcard in the
mail. Include, please, a section of your Activity Log with the
error notation. Several days worth of logging may help identify
the problem.
We try to thoroughly test each version before it is released but
an occasional bug may slip by. Any bugs will be squashed
immediately and an updated version released. Nordevald Software
does NOT believe that crashing is normal and to be expected.
Lock Ups
Some errors will lock your system up completely and DCI will not
be able to recover, hence no log entry will be made. In this
case, you will have to reboot. Errors of this variety are often
the result of door programs that lock up the comm port.
If the system locks up while you are typing, make sure you
haven't accidently pressed the PrintScreen key. If no printer is
132
attached to the computer, it will lock up for about 30 seconds
before the keyboard is functioning again. The HOLD key on Tandy
keyboards can cause similar problems. Press HOLD again to
release it.
The Most Frequent "Errors"
"No one can upload or download."
Make sure you have a protocol program, such as DSZ.COM or
GSZ.EXE in the DCI directory and Protocols defined, with
appropriate security levels, from the File Menu SysOp
Commands.
"DCI is reporting the wrong date/time."
DCI gets the date and time from your computer. Take the
board down and set the date and time using the DOS commands
or your CMOS Setup program.
"My doors/events won't run."
Check the activity log for any error messages.
"My doors/events have an error message of 2."
Error 2 means that DCI and DOS cannot locate the program.
Make sure it is in your DCI directory, DOORS directory, or
in a directory that is in your DOS PATH.
"My modem doesn't hang up."
Make sure you have your modem set to handle DTR normally.
"When I delete messages, they aren't renumbered."
DCIPurge will remove the deleted messages from the data file
and renumber the remaining messages.
133
GROUP ACCOUNTS
These are not really accounts but groups of users listed in a
text file.
When entering a private message, you may send mass mail to every
user who is listed in a text file by entering @ followed by the
name of the file at the TO: prompt. For instance, if the file is
named GROUP1.GRP, enter @GROUP1.GRP. When you save the message,
copies will be sent to all valid user names in the file.
If you wish to include the CC List in the text of your message,
you may do so by including the file (%%GROUP1.GRP).
Similarly, the Designated Receiver of a private file may also be
a group. Enter @<filename> as the Receiver. Anyone listed in
the file may download it.
When specifying a group file as the TO: of a message or the
designated receiver of a file, DCI will look for a file in the
DCI directory if it does not contain a pathname. If you include
the file in the message of the text, you will have to include the
pathname unless the file is in the \INCLUDE directory of the file
section.
134
INCLUDE FILES
Include Files are text files that are "included" in a message or
MNU file. They are not actually incorporated, but are displayed
so as to appear as a part of the message or MNU file.
To include a file in the text of a message, the file must be
located in the Include Directory. Users can upload text files to
this directory by selecting I)nclude Message when uploading.
When the message is posted, to include the file the user should
enter '%%' followed by the filename. For instance, if the
filename is MYFILE.TXT, the file code should be entered as
%%MYFILE.TXT. Both editors have commands that will allow the
user to view the message with the text of the include file
displayed. In the Non-ANSI editor, the command is /LF; in the
ANSI editor, ^QR.
If the Include file contains ANSI color or graphic codes, it
should be structured as the other MNU files are (see MNU files).
If a file is included that contains ANSI codes and not formatted
properly, its display will be aborted. The format %%<filename>
tells the system to display the file. The format %%<filename>%%
(e.g., %%BBSAD.TXT%%) will tell the system to determine the
correct section of the file to display based on the color and
graphics settings of the user who is reading the message. If you
do not wish to allow .TXT files to be uploaded but would like to
allow Include Files, you can designate that they end with a
specific extension, such as .MSG, and then enter that as one of
your Allowable Files in SYS: CONFIG.
Text files can also be included in MNU files by using the
%%<filename> code. These files must be stored in the DCI
directory. This is useful if you wish to run an external program
as an event to add a daily quote to the permanent section of the
main bulletin. Make sure the program creates the text file in
the DCI directory (or use a batch file to copy it) and enter the
name of the text file it creates in the MNU file as %%<filename>.
The contents of the include file will be displayed as part of the
MNU file display.
If the system cannot find an include file, a message will display
on the screen. If the user has CoSysOp access the full pathname
of the include file will be displayed to help correct the
problem. When reading a message that is displaying an Include
file pressing the spacebar will abort the Include file display.
To abort the display of the message, the spacebar will have to be
pressed again.
SysOps who find themselves continually answering the same
questions from users can create answer files and include them in
the reply messages. This allows for pleasant, detailed replies
from tired or frustrated SysOps and keeps users happy.
135
To include a text file that you do not want users to be able to
download or view, name the file <filename>.DCI. Users are
unable to download files with the .DCI extension. Make sure that
the name does not conflict with the name of the data file in the
subdirectory. Allowing include files from other directories
would compromise security. (Someone familiar with the setup of
your system would be able to display activity logs, et cetera.)
The SysOp may include files in messages that are not located in
the Include Directory. The fullpath name must be included in the
filename designation (%%path\filename%%).
136
LOG FILES
The log files are located in the LOGS directory. All are
accessible from the SYSOP: FILES command for viewing, editing,
purging, and searching. Each log has a specific purpose. If DCI
finds that a log doesn't exist, it will create it.
Activity Log
The Activity Log tracks all system activity with the exception of
most of the SysOp's actions. As a security feature, SysOp
activity can be logged. See SYSOP: CONFIG for details on
controlling messages to the Activity Log.
Some entries are capitalized as they are worthy of the SysOp's
attention.
When the board is put up or taken down, unless DCI was executed
with the /ONLINE switch, a notation is made in the activity log
along with the date and time. If the board goes down with an
error, the error is also noted.
Log On
When a user logs on, an entry is made listing:
<system name> (<real name>) <location> <time> <baud rate>
Last Call: <date>
The next entries reflect the user's activity on the system.
Log Off
When the user logs off one of the following entries is made:
Dropped carrier
Logged off normally
Exceeded time limit
Input time out
followed by:
<time> <date> <timeleft>/<timecredit>/<time limit>
C:<number of times called>
A new user will have additional information listed at logon:
CB:<callback verified?> LD:<long distance?> D:<data
phone number> V:<voice phone number> DOB:<date of
birth>
137
Main Menu Activity
Msg(s) read in : <base numbers>
Msg(s) added in : <base numbers>
Msg(s) del'd in : <base numbers>
Msg scan in : <base numbers>
Paged SysOp : <time>
Reason : <reason user entered>
Chatted with SysOp -- no log (SysOp did not log the chat)
Chatted with SysOp -- logged (SysOp created a log file of the
chat)
Board Menu
Configuration
Help
System Info : <M=main bulletin, F=file bulletin, bulletin
numbers
List Users
Checked Time
Utility Menu
Recent Callers
User Search : <username> <(entries not found)>
Ignore base : B#<base number> (<new base access>)
Logged New Msgs : <number of messages>
Logged My Msgs : <number of messages>
Modified base : <base name>
ADDED BASE : <base name>
Where Msgs
Prompt Beep (input time out at a prompt)
Editor Beep (input time out in an editor)
Alert File Displayed
Record Update
Added new user : <system name> (<real name>)
138
Dropped to DOS : <time>
Temp Sys Status : <time>
File Section Activity
File Section In : <time>
File Section Out : <time>
File scan : <search string>
File view : <filename>
Upload success : <protocol letter> <filename(s)>
Upload failure : <protocol letter> <filename(s)>
Not enough time : <protocol letter> <filename(s)>
Download success : <protocol letter> <filename(s)>
Download failure : <protocol letter> <filename(s)>
File ratio exc'd : <filename> Size: <filesize> Batch: total
size of files in batch queue> Free: <total
size of Free files>
File Stats : U:<K uploaded> D:<K downloaded> P:<user's
participation or n/a if no file ratio>
R:<user ratio?> FP:<file pig points>
File removed : <filename>
FILES MOVED : <number of files> from directory <directory
number>
Logon Attempts
LEGAL LOGON : <system name> (<logon entry>) <time> at
<baud rate>
LOGON ATTEMPT : <logon entry> <time> at <baud rate>
SLOW LOGON : <time> at <baud rate>
FAST LOGON : <time> at <baud rate>
Reg Attempt : <system name> (<real name>) <location>
(registration attempt)
139
Warnings
ATT SEC BREACH : dos (unsuccessful Drop to DOS)
ATT SEC BREACH : security level (unsuccessful Temporary
SysOp toggle)
ATT WRITE BASE : Base #<base number> -- <base status> (user
doesn't have write access to base)
ILLEGAL HANDLE : <handle> (Handle duplication or TrashN.LOG
entry)
FILE REM ATMPT : <filename> (user attempted to remove a file
s/he did not upload)
DISK SPACE LOW : File Section -- Uploads halted (Check Free
Space is ON, less than 1 meg on Upload
Drive)
FILE VIEW ATMPT : <filename> (no viewer defined for file
type)
File Sect Attpt (security level too low for access)
Add Base Attpt (security level too low for access)
Mod Base Attpt (security level too low for access)
Door Sect Attpt (security level too low for access)
SYSOP SECURITY LEVEL ATTEMPT: <user name> (attempt to increase
Group Security to SysOp Level)
ATTEMPT TO DELETE SYSOP! (let's hope it was line noise!)
Door Activity
Door Menu
DOOR ACCESS : <door filename> <begin time> <end time>
Door Time Low (user's time left less than 5 minutes)
DOOR ACC DENIED : <door name> part. low: <user's
participation>/<door participation>
DOS Activity
DCI CHILD RESULT : <filename> <comments depending on program>
DCI CHILD ERROR : <filename> <DOS exit code> <time>
DOS ERROR : <pathname> <filename> <DOS error code>
<time>
140
DOS ERROR : <event name> <DOS error code> <time>
CHILD ERROR : <filename> <DOS exit code> <time>
FILE ERROR : <filename>
FATAL ERROR : <filename>
Event Activity
NEXT EVENT : NONE (no events in queue or events OFF)
NEXT EVENT : <event name> at <time> on <date>
EVENT COMPLETED : <event name> at <time> on <date> Status:
<result>
EVENT FAILURE : <event name> at <time> on <date> Status:
<result>
Alert Log
When a user logs on, the ALERT.LOG is scanned for two entries:
the user's system name and SECURITYLEVEL. These can be followed
by either ALARM which will beep five times to alert you, or FILE
which will display a text file to the user, or both and the *A*
desgination will appear on the status line.
Security level alerts must contain the low and high security
levels; e.g., SECURITYLEVEL;50;60. This will trigger an alert
(either alarm or file display) for users with security levels
above 49 and below 61.
File alerts must be followed by a filename of no more than 12
characters. The file must be in the \LOGS subdirectory.
Sample ALERT.LOG entries:
USERNAME;ALARM;FILE;USERNAME.TXT
(when username logs on sound alarm and display
USERNAME.TXT)
SECURITYLEVEL0;10;FILE;TWIT.TXT
(if user security level 10 or less, display
TWIT.TXT)
Call Log
The Call Log records the logon time and date of all user's who
logon the board except the SysOp. To keep displays of Recent
Callers within reasonable limits, this log must be purged
regularly. This can be done as an internal event or from the
SYSOP: FILES menu.
141
Chat Log
The Chat Log records all logged chats. When you begin logging a
chat, an entry will be made in the log indicating the user's
name, and the current time and date.
Download Log
The Download Log is not maintained by the system. Most external
protocols maintain a log of all transfers in a file specified in
the DOS environment. If you are using more than one program for
external protocols, set them all to use the same log file rather
than separate files. Set the protocol variable to the LOGS
directory of your system.
For instance, entering SET DSZLOG=C:\DCI\LOGS\DOWNLOAD.LOG in
your CONFIG.SYS file will tell DSZ where to write transfer
information.
Failcall Log
The FailCall.Log contains information on users who log on as NEW.
All entries contain the basic information:
ATTEMPT: <system name> <real name> <location> D<data
number> V<voice number> <time> <date> <baud rate>
If the new user completes the registration process, no other
entries will be made in FAILCALL.LOG. However, if the user fails
to complete the process one of the following entries will be made
in the log:
DUPHANDLE: (User#<user number of current user> H#<handle number
of duplicate>)
The handle the new user selected is a duplicate of a
user's handle currently on the system.
DUP NAME: (H: <handle of current user with same name>)
The name the new user entered is a duplicate of a
user's real name already on the system.
DUP PHONE: Duplicate #: <real name of current user> (<handle of
current user>) V:<voice number of current user>
D:<data phone of current user>
Either the new user's data or voice phone number is
a duplicate of a current user's phone number.
ILLEGAL: Handle
ILLEGAL: Realname
ILLEGAL: Voice #
142
ILLEGAL: Data #
ILLEGAL: City
The specified entry was found in the TrashN or
TrashP log.
INCMPLT: User connected when called back but dropped carrier.
LONG DIST, 2nd try: The user failed in his first attempt at
long-distance callback and tried to logon again.
LONG DIST: The user's data line is long distance and
the board is not allowing long distance callers
access.
NOTERMS: The user answered No to the terms.
FAILCALL: The user failed to connect when called back, for one
of the following reasons:
NOCARRIER usually the call was answered voice
ERROR modem error
BUSY line was busy
NO DIALTONE no dial tone when modem tried to
dial
SYSOPABORT SysOp aborted callback by pressing H
TIMED OUT the modem waited over 60 seconds for
an answer
If the user fails to gain access for a reason other than not
answering the callback or dropping carrier, he will be given the
opportunity to leave feedback. Since this user does not have an
account, the feedback will be saved in the Failcall Log under the
entry listing the information he entered and the reason he failed
to complete the registration.
GoodArea Log
A GOODAREA.LOG is included that contains the area codes for
Canada and the United States. If a user's area code is not found
in this file during registration, the user will not be allowed to
continue.
If you can make a local call to another area code (by dialing the
seven digit phone number without the 1 or area code prefix),
include this area code both in the general listing of
GOODAREA.LOG and at the beginning of GOODAREA.LOG in parenthesis.
(813) denotes that phone numbers within the 813 area code are
local calls to you. 813 indicates that 813 is a valid area code.
143
To place local calls to another area code that must be dialed as
###-###-####, enter the area code at the beginning of the
GOODAREA.LOG as M### (area code 813 would be entered as M813).
LDPhone Log
This is the Long Distance Phone Log. If the user's area code
matches the board's area code, this log is checked to see if the
call is actually local.
Enter into this log all valid phone exchange numbers that are
local to your system. These are usually listed in your local
phone directory.
If there are exchanges within your area code that do not require
the 1- prefix, yet are still toll calls, enter them in the
LDPHONE.LOG as $<exchange>.
RegAlert Log
This log performs similarly to the alert log but is designed
specifically to issue alerts during the registration process.
The file is scanned for matching handle, first and last name, and
phone numbers. This is particularly useful if you have someone
who has forgotten a password and keeps trying to log on as new
but never leaves you a new password.
TrashN Log
This is the Trash Name Log. Enter any names or words in it that
you wish to prohibit. When a new user is registering, if his
name or handle is found as an entry in this log he will be given
a message that he has entered invalid information and given the
option to leave feedback to the SysOp. He will not be allowed to
complete registration. You can also include in this log words
that you do not wish to be entered as city names, such as
profanity.
Entries in the log must be in capital letters, one entry per
line.
144
TrashP Log
This is the Trash Phone Log. Enter any phone numbers of people
who you want to lock out of the board. The phone numbers must be
in the format:
(###)###-####.
Each entry must be on a separate line in the log.
This log is also used to distinguish invalid phone exchanges from
valid ones in your area. If a user enters a phone number that
contains an exchange not listed in the LDPHONE.LOG, the board
will assume that they have entered a number that is in your area
code, but long distance to your board. To guard against this,
you can enter invalid exchanges in the log file using the format
###-. It is a good idea to make entries such as 111-.
User Log
The User Log lists basic information, including real name,
handle, phone numbers, date of birth, city, and state, on all
users. See EXTERNAL UTILITIES for details.
145
MAINTENANCE
DCI boards require very little maintenance despite heavy user
activity. Most maintenance tasks only require initial set up by
the SysOp and can then be executed as an event and run without
the SysOp's watchful eye. The following are tasks that the SysOp
will need to perform periodically:
Check Activity Log
The Activity Log will notify you of any system problems that need
your attention, such as an event or door that didn't execute or
run correctly, or a protocol that is giving a lot of users
problems. Also check to make sure that new users are being
correctly added to the system based on their phone numbers and
your new-user setup.
Suggested: daily, purge when read.
Check Failcall Log
Any time you notice a registration attempt in the Activity Log,
check the Failcall Log for the matching entry to determine why
the user didn't complete the registration. Consistent call back
failures by multiple users could indicate a modem problem.
Suggested: as necessary.
Purge Call Log
An entry is added to the call log every time a user logs on the
board. This log is then used to display the Recent Caller
information from the Utility Menu. To prevent it from getting
too big it needs to be purged regularly. This can be done as an
event (see Events for the event definition of this) or you can do
it manually from the SYSOP: FILES Menu.
Suggested: purge as a twice weekly or daily event.
Back Up Board Files
No one wants to think about hard disk problems and corrupted
files but they are a fact of computing life. As a precaution,
back up the .DCI files regularly, particularly BOARD.DCI, the
main data file, and USER.DCI, the user file.
146
Back up all DCI files periodically (including .DCI files in the
file section), all .MSG and .HDR files, data files in the DOORS
directory, and MNU files, to either floppies or a tape. Below is
a batch file for the biweekly event.
Suggested: a biweekly event that calls a batch file to back these
up to a directory on your hard drive.
BackUp Batch File:
To back up important board data as a biweekly event, first create
a directory on your hard drive such as DCIBACK, then create the
batch file, DCIBACK.BAT and define it as a biweekly event.
The batch file should copy all .DCI files from the DCI directory
to the backup directory. For instance, the batch file might
read:
copy C:\DCI\*.DCI C:\DCIBACK
This will backup the main board data file, the user file, the
Information section data files, the protocol data files, and the
event data files and will only take a minute or two. It takes so
little time to run that you may want to do this as a daily event.
Deletion of Inactive Users
The smaller the userfile, the faster searches of it will be.
Users can be deleted as an event (see EVENTS).
Suggested: check once a month by S)earching the user file by Last
Call Date.
Deletion of Received E-Mail
The fewer messages in E-Mail, the faster users will be able to
access their messages. Keeping E-Mail limited to 500 messages
will keep search time to a minimum and should allow most users to
maintain a thread of E-Mail. When deleting received E-Mail, do
not delete the last 100 or so messages in the base to preserve
recent threads.
Suggested: weekly or as necessary.
Deletion of Old Messages
Do not allow message numbers in any one base to exceed 30,000.
Delete and Purge as necessary.
Suggested: as necessary.
147
Moving Uploaded Files
As the number of files in the Upload directory increases, you
will need to move them to their permanent directories. Users
specify which directory a file belongs in when it is uploaded.
Using the M)ass Move file option, check these settings. The
files can then be mass moved or you can set up an event to do it.
After a Mass Move, S)ort any directories that received new files
to maintain the alphabetized listings.
Suggested: check weekly or as file section activity dictates.
File Directory Size
Do not allow individual file listings to exceed 500 files as
supporting utilities will not be able to handle greater numbers.
If a file directory contains close to 500 files create a new
directory and Mass Move files into it. It is best to keep file
directories to 100 files or less to increase the speed of file
searches.
Suggested: as necessary.
Optimization
A bulletin board system is file intensive. Any software that
frequently updates numerous files will cause fragmentation of the
files on your hard drive. This makes your hard drive work harder
when searching for and reading files and reduces its performance.
Disk optimization software will reorganize the hard disk.
Remember: ALWAYS back up important DCI files to floppies before
running optimization utilities. Do NOT run these utilities as
events.
Suggested: monthly to quarterly.
148
PARAMETERS FOR DOORS/PROTOCOLS/EVENTS
External programs often need to be sent specific information in
order to run properly. Some of this information is repetitive or
is specific to the user that is online. DCI provides codes that
can be used to send this information. They will be interpreted
by DCI and sent to the program to be executed. Each code must be
preceded by a percent sign (%) and followed by a blank space.
For instance, if a program needs to know the user's name, the
baud rate, and the comm port, the parameters would be: %N %B %P.
Each time this program is run, the name and baud rate of the
current user online and the number of the active comm port will
be sent to the external program.
When modifying doors, events, and protocols DCI will display the
parameters as both coded and translated so you can see exactly
what information will be sent to the program.
Only letters preceded by a percent sign will be interpreted,
allowing for greater flexibility in sending parameters. The %Z
code will send the pathname of the DCI directory. If the program
needs the pathname of the \DOORS directory, enter %ZDOORS as part
of the parameter string. For instance, if the DCI directory is
C:\DCI, %ZDOORS will be translated to C:\DCI\DOORS.
External programs vary in the way the information they need
should be formatted. DCI provides several different ways of
sending some of this information.
For instance, external programs vary in the way that they
determine whether or not the user is at the local keyboard. Some
doors determine this by the word LOCAL in the command line. The
%Q code will be translated as LOCAL if the user is local and will
not be translated at all if the user is on from remote. The %O
command will be translated to 0 if the user is local or to the
active comm port number if the user is on from remote.
Similarly, more than one code is available to pass on color and
graphics setting information, and the user's name.
Several codes are available that are interpreted by DCI and not
passed on to the program being executed. These include a code to
tell DCI that the program updates the user's record, one to limit
the user's time in the door, and one to tell DCI that important
information has been altered and it needs to recycle.
149
Parameter Codes
The list below shows the codes, a brief explanation of what each
is translated to, and the format of the information that is sent.
A sends the actual baud rate of the user, useful with
locked bauding (300, 1200, 2400, 4800, 9600, 19200,
38400)
B sends the modem baud rate (300, 1200, 2400, 4800, 9600,
19200, 38400)
C user's color selection (C - yes, N - no)
C1 user's color selection (1 - yes, 0 - no)
D user's data phone number (##########)
E DCI exit (*** see caution below ***)
F user's transfer protocol letter (A-Z)
G user's graphics selection (G - yes, N - no)
G1 user's graphics selection (1 - yes, 0 - no)
H user's home city, state (city,state)
L user's time left this call in minutes
M limit user's time in door (*** see caution below ***)
N user's system name (blanks replaced by % eg., BOARD USER
would be sent as BOARD%USER)
N_ user's system name (blanks replaced by _ eg., BOARD USER
would be sent as BOARD_USER)
O active comport with 0 for local (0, 1, 2, 3, 4)
P active comport (1, 2, 3, 4)
Q local? (LOCAL or nothing if not local)
R user's record number
S user's security level
T current time (HH:MM)
U user's record update indication (*** see caution below
***)
V user's birth date (MMDDYY)
X path to message data files
Y path to upload directory
Z pathname of DCI directory
DCI Exit
This parameter is for utility doors and events that alter data
that DCI keeps in memory. The %E parameter will insure that once
the utility program runs, the board will halt. Make sure the
board is running in a looping batch file if any of these
utilities are set as events or run as doors from remote.
Warning: do NOT use this parameter unless the utility's
documentation specifically states it is necessary.
Limiting Door Time
The %M parameter may be used to limit users' time in doors that
do not allow you to restrict door time. To use this parameter,
the maximum number of minutes that a user can spend in the door
should be immediately following it, e.g. %M15. This value must
be greater than 0 and less than 256. Caution: do not use this
parameter with doors that write to the DCI user record.
150
The parameter will be compared to the user's actual online time
remaining. The user will be granted the lesser of the two in the
door. For instance, if you set %M20 and the user has 10 minutes
online time left, the user will be allowed 10 minutes in the
door.
Updating the User Record
The %U code is used if the user's record needs to be updated
after leaving a door. This is necessary with some programs that
modify the user's record if the changes need to be effective
immediately, such as granting base access with the Auto Access
Door. It is interpreted by the system and not sent to the
external program.
User Name Format
When passing information on a command line to an external
program, the information is separated by spaces. For instance,
if a door wanted the user's handle followed by the user's time
left, the string would look like TYPICAL USER 30. Most programs
would interpret this as the user's name being "TYPICAL" and then
expect the time to be in the next string, in this case "USER"
which would cause an error.
DCI does not pass the user's first and last name to a door, but
will pass the user's system name (if the board does not support
handles, this will be the user's first and last name). The spaces
in the user's system name must be replaced by another character.
The %N parameter will be translated to the user's name with a
percent sign replacing the strings. The %N_ parameter will tell
the system to replace the spaces with underlines.
%N = TYPICAL%USER.
%N_ = TYPICAL_USER.
If the external program expects both a first and last name on the
command line, use the N parameter of your choice followed by 3
spaces. The second space will be interpreted as the user's last
name.
151
PROTOCOLS
DCI contains no internal protocols, as protocols are improved so
rapidly and the best are written by programmers who devote all
their time to the development of such. We strongly recommend the
use of Omen Technology's DSZ.COM or GSZ.EXE. Both contain
numerous protocols in a relatively small program and perform very
reliably.
Choosing Protocols
When deciding on what protocols to use, select only those that
meet the following criteria:
The program returns an exit code of 0 when the file transfer
is successful and a nonzero exit code when the transfer
fails. DCI uses these exit codes to determine how to
correctly update the user's record.
The program does not freeze if a user drops carrier during a
transfer.
The program accepts file names with full pathnames so that
users can download a file without being in the directory
that contains the file.
The program maintains a log of all transfer activity. This
will allow you to determine if someone is abusing your
system by downloading files and aborting them at the end of
the transfer (actually receiving the file), which tricks the
protocol into concluding that the transfer was not
successful.
Whenever you set up a new protocol, test it to make sure it works
correctly under a variety of situations before allowing users to
use it. Drop carrier during transfers, abort the transfer at
various points, and download files from multiple directories. If
a protocol has only a few small quirks, chances are a user will
stumble over them. It is best not to use such a protocol. Put
file viewers through similar tests.
Protocol Fields
The protocol information saved by DCI is very similar to the door
information. Each protocol record contains the following fields:
Status
Disabled : This record is not used and will be removed when the
data file is purged.
Inactive : The protocol is unavailable; it will not be purged
unless information is not complete.
Active : This protocol is available for use.
152
File Name
The full file name, including extension, of the external program.
The file must be in the Main DCI Directory.
Name
The name (up to 22 characters) that the users will see on the
protocol menu or when transferring a file (i.e. XMODEM CRC). If
the protocol supports batch transfers and you set it up as a
batch type (see Type below), include the word "Batch" in this
entry.
Access Level
This is the minimum security level necessary to use the protocol.
When testing new protocols it is best to restrict it to a few
people.
Letter
The letter used to record the user's default protocol in the user
record (cannot be a duplicate of another protocol's letter). Try
to adhere to standard protocol lettering (X for Xmodem, C for
Xmodem CRC, et cetera).
Type
This field tells DCI what the program does. In the case of
protocols, the batch designation activates the Batch Queue when a
user enters the file section. The types of viewers are used to
determine if a viewer is available for the type of file the user
wishes to view (files with the extensions .TXT, .DOC, and .MSG
are viewed by an internal DCI procedure). This field is set to
one of the following:
Single file transfer protocol
Batch file transfer protocol
ZIP viewer
LZH viewer
ARC viewer
GIF viewer
Send Parm String
This is the list of parameters necessary for the external
protocol to send a file to the user or for the viewer to access a
file. Most protocols require that the last parameter is the
name(s) of the file(s) being transferred. DCI automatically adds
these to the end of the parameter string (see PARAMETERS).
Receive Parm String
This is the list of parameters necessary for the external
protocol to receive a file from the user. Most protocols require
that the name(s) of the file(s) being transferred be sent as the
last parameter. DCI automatically adds these to the parameter
string. (Viewers do not have receive parameters [see
PARAMETERS]).
153
Protocol SysOp Commands
From the SysOp File Menu, select P)rotocols. The following
commands are then available:
Add
The Add command allows you to add a new record to the protocol
data file maintained by DCI. You will be prompted to enter
information for each field in the record. Until you have
completely added all the necessary data and are ready to test the
protocol, set it to Inactive. E)xit and S)ave the information.
DCI allows for a total of 29 protocol and viewer records. This
includes any records with a status of Deleted. If you try to Add
a new protocol or viewer when there are already 29 defined, a
warning message will display and you will have to delete one or
purge the deleted records before adding the new one.
Modify
The Modify command allows you to change any of the existing
protocol records. Once you enter the number of the record to
modify, you will be presented with a menu showing the existing
settings. The A)ll option is available when adding a new record
or when the current one has a status of Deleted. This option
will prompt you for each field of the definition in order,
overwriting any existing fields in the record.
To alter any definition, select the appropriate number from the
menu. When you E)xit, you will have the opportunity to S)ave all
the changes you have made.
Each time a user enters the file section the system checks to see
if his protocol is active. If it is not, when he attempts to
transfer a file he will be prompted to change his protocol.
Thus, if you disable a protocol you need not worry that it will
cause problems for the users (other than the inconvenience of
having to select another one) or hang the system.
List
This command will display a list of all the protocol records and
most of the information contained in each one.
This is a sample listing:
File Name Status Sec Letter Display Name Type
1. TRANSFER.EXE Active 60 F FastModem Single
2. TRANSFER.EXE Active 60 Q QwikModem Batch Batch
3. LOOKSEE.EXE Active 60 l LookSee Zip ZIP view
4. GOFILEGO.COM Inact 255 G GoGoModem Batch Batch
5. BUGGY.EXE Dele'd 255 B BugsModem Single
The first two protocols use the same file with different
parameters (not shown) to invoke two different protocols, one
that supports single file transfers and another that supports
batch transfers.
154
Only the Active protocols will be displayed on the Protocol Menu
when the user selects Transfer Protocol from the File Menu. The
Protocol Menu displays each active protocol's Letter and Display
Name. When the user selects a protocol, the protocol letter is
stored in the user's record to indicate his default protocol.
Purge
This command will remove any records from the protocol file that
have a status of Deleted. When you change the status of a record
to Deleted, Purge the file as it will increase the speed of
record searches.
Rearrange
This allows you to rearrange the order of the records in the
protocol file. The Protocol Menu displays the protocol names in
the order that they are stored.
Sort
This command will sort the records in the protocol file
alphabetically by Display Name.
155
RATIOS/PARTICIPATION
Types of File Ratios
The file ratio can be determined by either the number of files
transferred or by the size of the files transferred.
The file ratio is the ratio a user must maintain in order to
download files. If you choose a ratio of 1:10 then the user must
upload 1k or 1 file for every 10k or 10 files downloaded to
continue to download. If you do not wish to impose a ratio, you
can set this value to 0. You may also incorporate a user
participation factor into the ratio.
Participation
A user's participation is determined by message base activity,
reading and posting. The Participation value in the user record
is based on posts made by the user and is a "bonus" when
determining overall board participation, and recognizes those
users who post heavily in only a few bases. New users are given
"extra credit" during the first 6 calls.
If you do not wish to use the participation factor, set it to 0;
otherwise, set it at the amount of participation you expect from
the users of your system. It is a percentage and can set from 1
to 100%.
Combined Ratio and Participation
Several values are involved in combining the board participation
factor and the user's ratio, which is then compared to the board
ratio to determine whether the download is allowed.
The weight that a user's participation has on downloading
privileges is determined and then compared to the value of the
board participation that you have selected. For instance, if you
set board participation at 50% and the user has 50%
participation, then the user's relative participation will be
100%. Users whose participation is higher than 50%, would have
relative participation values greater than 100%, with a maximum
of 200%.
Board User Relative
100 100 100
75 100 133
75 75 100
75 50 66
75 25 33
50 100 200
50 75 133
50 50 100
50 25 50
156
It is the Relative Participation that combines with the
upload/download ratio and is expressed in the user's S)tats in
the File Section.
When the user wants to download a file, his actual
upload/download ratio is computed and then multiplied by his
relative participation factor. The effect is that someone who
participates at the level that you expect will be dealing with
his actual ul/dl ratio (multiplied by 1.00), someone who doesn't
participate as much will have an elevated ul/dl ratio, and
someone who participates more than you expect will have a lowered
ul/dl ratio (as low as one half of the board ratio).
Participation Ratio
Board User Relative Board User Relative DL
100 100 100 1:10 1:10 1:10 Yes
75 100 133 1:10 1:10 1:13 Yes
75 75 100 1:10 1:10 1:10 Yes
75 50 66 1:10 1:10 1:7 No
75 25 33 1:10 1:10 1:3 No
50 100 200 1:10 1:10 1:20 Yes
50 75 133 1:10 1:10 1:13 Yes
50 50 100 1:10 1:10 1:10 Yes
50 25 50 1:10 1:10 1:5 No
New users are given "extra credit" upload points when the ratio
is computed so that they may download without uploading if you
have the participation factor set at less than 100%. The amount
of the credit is determined by comparing the board ratio and
participation factor. The lower the participation factor, the
higher the credit.
CoSysOps are automatically given a relative participation of
100%. You can also modify a user's record and turn their ratio
off.
Free Downloads
You can designate selected files as free, such as information
files on your system or file compression utilities. They will
not be added to the user's download statistics nor will they be
figured in the download ratio.
To set up a directory of free files add a file directory and
create its DOS directory with a name beginning with the word
"FREE". For instance, "FREETEXT", "FREEUTIL", or "FREE1".
To allow users to download files regardless of how much time they
have left on the system and regardless of their ratio setting,
set up the directory with a name beginning with the word "TIME".
The time the user spends downloading files from such a directory
will be credited completely when the download is complete.
157
SECURITY
Security is of prime importance on a bulletin board system. DCI
allows you to configure the system to give users a great deal of
freedom or very little. There are many levels of security on a
DCI system.
System Access
Callback verification of new users is the first level of advanced
security on a DCI board. Random callback and callback at every
logon increase security tremendously.
Another option is the use of a Private Logon Password. Callers
will connect but there will be nothing on the screen. If they
enter the Private Logon Password correctly, the logon prompt will
then appear.
New User Registration and Access
If you wish to run a private system, set Allow New Users to NO.
No one will be able to logon as NEW and gain access to the
system. They will have an opportunity to leave feedback to the
SysOp. In this way, you can request applications for access.
If you do allow new users, setting Local and Long Distance
Callback to YES will ensure that you have a verified phone number
on each user who does gain access to the system. This is by no
means fail proof, but it does afford a degree of security far
above that of trusting users to provide you with identifying
information.
If you do Allow Long Distance Users and do not use the Long
Distance Callback, to guard against those who enter invalid phone
numbers just to gain access you should consider restricting their
access to the system more than you would the local new user. You
can do this by setting the Unverified Security Level and Time
lower than that of those for Verified Users.
The Verified Security Level and Main and File Command Options
that you allow are the next step in controlling access to the
system. In conjunction with the Access levels you have set for
the door sections, individual doors, individual bases, the file
section, and handles, the new user will only have access to those
areas of the system that you deem appropriate.
When a new user enters registration information, the user's real
name, handle (if allowed), and phone numbers are checked against
all the entries in the user file. If any of these match the
information of an existing user the registration process is
aborted, an explanation is noted in the Failcall Log (including
information on the current user with matching information), and
the user is logged off after having the opportunity to leave
feedback.
158
The TrashN (name) and TrashP (phone) logs allow you to keep out
people who have not behaved appropriately on your system. The
other phone logs help to ensure that users are entering valid
phone number information.
See also SYSOP: CONFIGURATION, New Users and Modem Setup; DISPLAY
FILES, Register.mnu; LOG FILES, Activity Log, Failcall Log,
GoodArea Log, LDPhone Log, RegAlert Log, TrashN Log, and TrashP
Log; and the remainder of the SECURITY section.
CoSysOps
DCI allows you to decide the complete security level structure of
your system, including defining the security level necessary to
have access to the CoSysOp functions. The SysOp security level
is 255. Set the CoSysOp security level at less than 255.
CoSysOps have access to all the SysOp Functions with these
exceptions:
CoSysOps may NOT view or alter a SysOp's account.
CoSysOps may NOT delete a message the SysOp posted using
his System Name.
CoSysOps may NOT access the Board Directories section of
the Board Configuration.
CoSysOps may NOT access files in the Private Directory
protected with the SysOp File Password.
CoSysOps may NOT use the Other File viewing, editing, and
searching feature in the SysOp Files area.
TempSysOp
This gives the user currently online temporary SysOp access
including a security level of 255 and full main and file command
options. Use this feature with caution. The user will retain
the SysOp access until you toggle it back off with Alt-T or the
user logs off the board. When a user has Temporary SysOp access
a highlighted *T* will appear on the status line and the message
"Temporary SysOp Access!" will appear above base prompts as a
reminder.
Messages and Bases
To protect the users' privacy, private messages and messages
posted in private bases are not displayed on the local screen
when a user is on from remote. Pressing the F6 key on the local
keyboard will allow these messages to be displayed locally or
Base Visibility option will allow messages in bases other than E-
Mail to display on the local screen.
159
When a user enters a private base or E-Mail, the message screen
will be blanked unless the SysOp presses the F6 key. The same
occurs if a user enters a private message in an open base.
Feedback at logoff and at chat is blanked although new user
feedback is not.
On boards that allow handles, unless the user has opted to use
his real name as his system name it will never be displayed on
the board. It is only available on the status line and in the
user record.
Users' access to each base can be controlled through the security
level settings on the base as well as through the individual user
record. Several levels of base access, including locking the
user out completely, are available. With a lock out, the user
can not gain access to the base unless the SysOp specifically
changes it.
Doors
Access to the door sections as well as to individual doors can be
controlled by security level.
There is no option to pass a user's real name (unless it is also
his handle) or password to a door. Certain door interface files
request this information. The user's handle is inserted as his
real name, and the word "PASSWORD" is entered as his password.
SysOp Read
Normally, the SysOp sees the message headers just as any user.
However, the SysOp can press the F5 key on the local keyboard
which will display the system names of the posters next to their
handles. Pressing this key at the Search prompt will allow the
SysOp to use any search criteria regardless of message base
format. For instance, messages in an anonymous base could be
searched by date.
Include Files
These files may be located in either the Include Directory (when
included in the text of a message) and the DCI Directory (when
included in an MNU file). Allowing Include Files from other
directories would jeopardize the security of your files,
particularly log files. The SysOp may, in some instances,
include files from other directories (see INCLUDE FILES for
details).
File Section
The file section contains internal security measures. No file
with the extension .DCI may be accessed by a regular user nor can
such a file be uploaded.
160
The SysOp also has complete control over users' access to private
directories other than directory 0. The files in directory 0 are
only available to those users who know the full file name and
password (provided it is not the SysOp password) of the
particular file.
Only files in directories that the user has full access to may be
viewed. Only the SysOp or a user with Temporary SysOp Access can
view files in Directory 0.
161
STATUS LINE
The status line on the bottom of the screen when a user logs on
displays information about the user, allows you to change the
user's settings, and allows you to display and change system
information.
NOTE: If Direct Video (SYSOP: CONFIG: Miscellaneous)
is set to NO, the Status Line will not appear
on the local screen.
When a user logs on the status line appears, displaying
information about the user. There are five user information
status lines. Pressing F1 will rotate through these.
User Status Line I
<System Name> TL<time left in minutes> SL<security level> <last
call date> C:<number of times called> <baud rate [MNP
connection]><system time>.
User Status Line II
<First and Last Name> D:<data line number> V:<voice number>
B:<date of birth> <system time>.
User Status Line III
R:<file ratio?> UK:<K uploaded> DK:<K downloaded>
UD:<upload:download ratio> MP:<message post participation>
P:<system participation> OKD:<relative user ratio> TP:<transfer
protocol> <system time>.
User Status Line IV
Note: <user record note>
User Status Line V
Chat Reason: <reason user entered at chat prompt>
The last status line only appears if the user has requested chat.
162
When a new user is logging on there are two status lines that can
be toggled by F1:
New User Status Line I
REGISTERING NEW USER: <system name> (<first and last name>)
<baud rate [MNP connection]>.
New User Status Line II
D:<data line number> V:<voice phone number>.
Command Status Lines remind you of which key to press to modify
user or system settings. The settings can either be turned on or
off (those followed by a single arrow) or increased or decreased
(those followed by two arrows). The direction the arrow points
tells you the result of pressing the key.
Pressing F2 will rotate between command status lines:
Command Line I
F3- decrease user's session time by 5 minutes
F4- increase user's session time by 1 minute
F5- toggle SysOp Read
F6- toggle Private Display
F7- toggle SysOp Page
F8- decrease user's security level by 5 minutes
F9- increase user's security level by 1 minute
F10- toggle SysOp Next
Command Line II
ALT C- chat (break in immediately)
E- event information
H- hang up modem
J- jump to DOS
N- nice chat toggle
T- temporary SysOp status
^HOM- storm key
163
Command Line III
FR:<board file ratio> PF:<participation> ULC:<upload
compensation> FS:<file section security level>.
ALT F3- decrease board file ratio by 1.
F4- increase board file ratio by 1.
F5- decrease board participation by 1.
F6- increase board participation by 1.
F7- decrease upload compensation by 1.
F8- increase upload compensation by 1.
F9- decrease file section access level by 1.
F10- increase file section access level by 1.
Command Line IV
CTL: DOORS:<door security level> HANDLES:<handle security level>
ADDBASE:<add base security level> SOUND:
CTL F3- decrease door security level by 1.
F4- increase door security level by 1.
F5- decrease handle security level by 1.
F6- increase handle security level by 1.
F7- decrease add a base security level by 1.
F8- increase add a base security level by 1.
F9- toggle Sound.
164
Command Line V
SHF: NEW:<allow new users> CB:<callback verification>
SL:<verified security level> LD:<allow long distance users> UV
SL:<unverified security level>.
SHF F3 toggle Allow New Users.
F4 toggle local callback verification.
F5 decrease verified security level by 1.
F6 increase verified security level by 1.
F7 toggle Allow Long Distance Callers.
F8 decrease unverified security level by 1.
F9 increase unverified security level by 1.
Unlisted Commands
ALT L log user back on without disconnecting.
ALT M execute SysOp macro (see below)
ALT P changes user's protocol to 'n' (not valid).
ALT R toggles user's file ratio off and on.
ALT V if user's time and security level are less than
Verified Security Level and Time, increase the
user's settings (security level, time, handles
allowed, main and file options) to verified
levels.
ALT Z clears the local screen.
SysOp Macros are keystroke macros contained in MACRO.DCI. Create
file MACRO.DCI in DCI directory. Enter one macro per line
(maximum 255 characters). The macros are assumed to be numbered
sequentially (i.e., the first macro in the file becomes macro
#1). Lines in MACRO.DCI beginning with a semicolon (;) may
contain comments. Comment lines are not counted in the numbering
of the macros. ASCII 15 and ASCII 175 will be interpreted as
carriage returns. To execute a macro, enter Alt-M at almost any
prompt and then enter the number of the macro to execute at the
prompt.
165
TIME
Users' time limits can be enforced as either Daily or Session.
Session time limits allow the user to call as often as he wishes
and to use his total time limit per call. If designated as
Daily, the user can call as often as he wishes but may not exceed
his time limit in total online time per day.
Daily time limits are reset at midnight. A user who is online at
midnight will be under his next day's time limit at that point.
For instance, a user is allowed 45 minutes per day. His first
call of the day is at 11:55 p.m. At midnight, his next day's
time limit goes into effect. He may stay online until 12:45 a.m.
Had the same user called (first call) at 11:15 p.m., he would be
allowed to stay online until 12:45 a.m., using his full time
limit on both days.
DCI automatically provides that all users are given five more
minutes should they exceed their time limit for the day. This is
to allow a user to log back on to exchange an important message.
It is strictly a courtesy. If a user abuses this privilege, you
can disable (SYSOP: USER Modify Extra Options).
When a user's time has fallen below 6 minutes, he will not be
allowed to access door programs. This is to guard against door
programs that do not correctly calculate time.
The system constantly checks the user's time and will log a user
off when his time limit has been exceeded. The user will have
the opportunity to leave feedback. However, a user will not be
interrupted and logged off while posting a message if Allow
Overtime Usage is set to YES (SYSOP: CONFIG).
At the logon prompt, if the user has not entered any input after
30 seconds, the system will display "GOODBYE" and disconnect.
At other prompts the system will beep if the user has not entered
any input in 90 seconds, and again at 120 and 150 seconds. If
the user still has not entered any input after three minutes, the
system will log him off. SysOps and CoSysOps are given six
minutes before input time out and log off if on from remote and
ten minutes if on from the local keyboard.
166
ACKNOWLEDGEMENTS
Many people contributed to the development of this software.
First and foremost is Daniel Brewer, who is responsible for the
initial concept as well as the motivation to write the BBS. He
diligently coded the first version in April 1988. Dan is
credited with the original design of the ANSI editor and
installation program, and has helped in both the design and
coding of many features of the software.
Without Bill Weinheimer's helpful beta testing, suggestions, and
constant support, this would still be a homegrown system running
only on my computer. Bill is also directly responsible for the
Nordevald Callback Verification Door for Searchlight BBS.
Special thanks also to Blair Phillips, the second registered DCI
SysOp, for his many helpful suggestions, support, and diligent
bug tracking, not to mention his detailed research and
benchmarking of compatible doors.
Heartfelt thanks to Wes Cowley of Bird Lake Software for his
perseverance, wit, warmth, and attention to detail. Never have I
received such devastating yet tactful bug reports, and so early
in the morning, too. Wes is responsible for DCI's DESQview(tm)
awareness, the DESQview(tm) section of the documentation,
DESQview(tm) utilities for DCI (DCIDVKIT.ZIP), and the Bird Lake
User Purge Utility. Wes runs Bird Lake BBS, (813)265-3256, and
can be reached on BIX as wcowley.
And all the Nordevald Software BBS users who helped make this
software that users love. Special thanks to Larry Clapp, Derek
Glidden, and David Muntyan.
Version 3.00 updates: Wes Cowley is now a full partner in
Nordevald Software. David Interlandi, SysOp of Dave's Lookout,
has been honored with the title of Head DCI Cheerleader. Eric
Neff, SysOp of Longbow BBS at (813)961-3653, and John Folsom,
SysOp of OMNIBUS at (619)464-6271, have become Official DCI Beta
Testers and Authorized DCI Distribution Sites.
167
APPENDIX A - MODEM SETTINGS
With the myriad of settings available on most modems, it's easy
to feel overwhelmed at the thought of setting the modem to work
with the software. However, DCI only requires the following:
Recognition of NO DIAL TONE, BUSY, and NO ANSWER result codes
(Command X4, X6, or X7)
Result codes displayed
(Command Q0)
Auto Answer suppressed
(Command S0=0)
Reset modem on drop of DTR
(Command &D3)
DCD on/high indicates carrier
(Command &C1)
Please note that the commands listed above will work with most
Hayes compatible modems. Do check your modem manual to verify
that they will have the desired effects.
If you have Caller ID on your board line, or for some other
reason do not want the modem to answer on the first ring, set
Rings to Answer (SYSOP: CONFIG Modem). The modem must have auto
answer disabled regardless of this setting.
The following pages detail the settings on specific modems. This
information is provided by DCI SysOps.
A1
Practical Peripherals PM9600SA
Board Settings:
Modem INIT String : ATZ0
Modem Local String : ATH1
Modem Hangup String : ATH0
Minimum Baud Rate : 1200
Maximum Baud (DTE) : 38400
Locked Baud : YES
Default Settings:
In the term mode, enter: AT&F&W0
ATE0M0TW2&C1&D2&Y0&W0
/INIT
To verify proper setup, enter: AT&V
The ACTIVE PROFILE displayed should include the following:
DTE:38400 DCE:9600 PARITY:NONE
B16 B1 B41 B60 E0 L0 M0 N1 Q0 T V1 W2 X4 Y0 &C1 &D2 &K3 &Q5 &S0
&U0 &Y0
S00:000 S09:006 S10:014 S25:005 S30:000 S36:007 S37:000 S38:020
S46:138 S48:007 S82:128 S95:000
The above assumes that Stored Profile 0 will be used for normal
BBS operation. To utilize Profile 1, substitute ATZ1 for ATZ0,
&W1 for &W0 and &Y1 for &Y0. ATH0 should be used as the Modem
Hangup String in lieu of ATZ to ensure that LOGOFF.MNU graphics
and the DCI closing signature line will display fully at DTE
rates greater than 9600 BPS. NOTE: The DCI terminal screen will
scroll off the first two lines of the ACTIVE PROFILE display if
left to its own devices. Immediately hit the <PAUSE> key after
entering AT&V to pause the screen.
Information provided by John Folsom with the help of Eric Neff.
A2
USRobotics Courier HST 14.4 Modem
Dip Switches:
OFF: 1, 2, 4, 6, 7, 9, 10
ON : 3, 5, 8
Default Settings:
B1 F1 M0 X6
&A2 &B1 &G0 &H1 &I0 &J0 &K1 &L0
&M4 &N0 &P0 &R2 &S0 &X0 &Y1
Register Settings:
S02=043 S03=013 S04=010 S05=008
S06=002 S07=030 S08=002 S09=006
S10=007 S11=055 S12=050 S13=000
S15=000* S19=000 S21=010 S22=017
S23=019 S24=150 S26=000 S27=000
S28=008 S38=000
Board Settings:
Modem Init String : ATV1 S15=8
Modem Local String : ATH1
Modem Hangup String : ATZ
Set MaxBaud to 38400 and turn locked baud ON.
DCI doors and DSZ should be passed the %B parameter, not the
%A.
The S15 register should be set to either 0 or 8.
Information provided by Marianne Love.
A3
USRobotics Courier 2400 Modem
Dip Switches:
OFF: 1, 2, 4, 6, 7, 9, 10, quad
ON : 3, 5, 8
Default Settings:
C1 E1 F1 M1 Q0 V1 X1
Register Settings:
S00=000 S01=000 S02=043 S03=013
S04=010 S05=008 S06=002 S07=030
S08=002 S09=006 S10=007 S11=000
Board Settings:
Modem Init String : ATZ X4 V0
Modem Local String : AT M0 H1 Q1
Modem Hangup String : ~~~+++~~~ATH0
Information provided by Wes Cowley.
A4
Viva Modem 24
Default Settings:
B1 E0 L1 M0 Q0 V1 X4 Y0
&C1 &D2 &J0 &L0 &P0 &X0 &G0 &Y0
Register Settings:
S02=043 S03=013 S04=010 S05=008
S06=002 S07=030 S08=002 S09=006
S10=014 S11=070 S12=050 S14=168
S16=000 S18=000 S21=048 S22=113
S23=023 S25=005
Board Settings:
Modem Init String : ATS0=0
-- or --
Modem Init String : ATS0=0 V0 M0 X4 Q0
Modem Local String : ATH1
Modem Hangup String : ATZ
Often the Viva will ignore the Q0 command unless it is the last
command in the string.
Information provided by Marianne Love.
A5
APPENDIX B - NORDEVALD SUPPORTING SOFTWARE
Nordevald Software is continually developing software to work in
conjunction with the DCI BBS software. The following software is
designed to work uniquely with DCI systems.
All DCI Supporting Software is designed to be easy to install and
virtually maintenance free. The only setup is the creation of
the door and/or event record via the DCI internal SysOp commands.
The documentation of these programs contains full door/event
record examples with step by step setup information. All DCI
Supporting Software returns error codes that are fully explained
in the documentation of each program with helpful hints as to the
nature of the problem. Event and Door activity is also noted in
your DCI Activity Log. Each of the following programs will run
as a door and/or event on a system with 512K RAM or more.
All doors and utilities in full release are covered in the
following pages. Each section contains the full software
documentation. The registration and order forms are in Appendix
E.
Version
To check the version and compilation date of any of the following
software, at the DOS prompt type <program name> /VERSION.
Support
Support for these programs is available on Nordevald Software BBS
in the DOORS: DCI & Otherwise base.
B1
DCI Auto Access Door
Copyright 1990-91 Marianne Love, Nordevald Software
The Auto Access Door is compatible with DCI BBS Software, V.3.xx.
The Auto Access Door was written to provide a means for users to
select access to specific private bases without the SysOp or
SigOp manually giving them access.
The door can be configured to allow auto access to one or more
bases based on security level and, if you wish, age.
If the door is set up for multiple bases, the user will be
presented with a menu to select from. The user is presented with
a text file explaining the base and any special considerations,
and then asked if s/he wishes to join the base. If the user
answers Yes to the access prompt, the user will be granted
immediate access to the base and can enter it upon exit from the
door.
Installation
Copy DCIABASE.EXE to your /DOORS subdirectory and Add the entry
to your Doors Data File:
Status : Active
Filename : DCIABASE.EXE
Name : <see note below>
Access Level : <see note below>
Parm Type : DCI
Part. : <your choice>
Parm String : <see note below>
Description : <your choice>
To configure the door to grant access to only one base, such as
base 10:
Name : Access to base 10 <descriptive of purpose>
Parm String : 10 %U <base number, update user record>
If the base has a minimum security level for access it is best to
set the Door Access Level to this security level so that users
who have security levels below the minimum will not even see the
door listed in the door menu.
To configure the door to grant access to multiple bases:
Name : Auto Base Access <descriptive of purpose>
B2
Parm String : %U <update user record>
If any of the bases have a minimum security level, set the Door
Access Level equal to the lowest minimum security level of all
the bases selected for auto access.
Configuration
Run the Door and select M)odify at the prompt.
You will be shown the following:
Status : (Deleted, Disabled, Active)
Base Number : (number of the base)
Base Name : (name of the base)
Minimum Sec : (minimum user security level for access)
Maximum Sec : (maximum user security level for access)
Minimum Age : (minimum user age for access)
Maximum Age : (maximum user age for access)
Info File : (the name of the file to display)
Whenever the status of a record is set to Deleted, you can select
A>ll to enter each record field without returning to the
definition menu.
If you do not wish to restrict access to the base based on age,
then enter 0 in both the minimum and maximum age fields.
The info file should have the extension .AAB and be placed in the
/DOORS subdirectory.
If you change the base name, the base number will change
accordingly and vice versa.
When you are ready to allow access, change the Status to Active.
You may select the T>est Info File option to see how the file
will display. The presentation will be identical to the one a
user would see, including all prompts. However, the access
prompt will not alter your user record if you answer "Yes".
If you have an external editor configured for DCI, you will have
the option to E>dit the Info File from within the door provided
there is sufficient memory to shell to the editor.
B3
The Data File
To list all information, select L)ist from the Modify Prompt.
This will list each entry under the following header:
_ entry number minimum & maximum minimum & maximum
| _ base number security levels_ age settings
| | _base name | | display
| | | Sec Lev Age |
# Base Name Status Min Max Min Max FileName
=================================================================
To modify an entry, enter the entry number.
Status
Active - users meeting security level and age requirements have
access
Inactive - only SysOp and CoSysOp have access for modifications,
will not be removed from data file when P)urged.
Deleted - only SysOp and CoSysOp have access for modifications,
will be removed from data file when P)urged.
Deletions
Changing the Status of a door does not delete the information
from the data file. To prevent the file from becoming too large,
after several deletions, select P)urge to remove the deleted
entries.
Sort
If you have several bases set up for Auto Access, you may sort
them by base number so that they are listed in the Menu
numerically.
Door Activity
The door will update the DCI ACTIVITY.LOG with one of these
entries preceded by "DCI CHILD RESULT":
Auto Access Granted: <base number & name>
Auto Access Denied : (age) <base number & name>
Auto Access Denied : (locked out) <base number & name>
Access denied (age) occurs when the user does not meet the
minimum or maximum age requirements of the base.
B4
Access denied (locked out) occurs when the user has been locked
out of the base by the SysOp (by making the base unavailable via
Modify User in the DCI SysOp Options). If the user is locked
out, even if he meets the security level and age requirements, he
will not get access.
Maintenance
If you delete a base that has an Auto Access entry, do not forget
to delete the entry as well.
If you change the name of a base, modify the entry to reflect the
new base name.
Errors
All errors will be listed in the Activity Log.
An entry reading "AUTOBASE HALT Code=2" indicates that a user
entered the door and no bases were set up for Auto Access.
Please set the door status to Inactive until you have set up at
least one base for Auto Access.
An entry reading "DOS ERROR: <external editor name> 8" indicates
that there was not enough memory to run the editor from within
the door. This is not unusual considering the board and the door
are already residing in memory. If you have an external editor
defined, you can edit the Display Files from within DCI by using
the SYSOP: FILES Edit Other option.
B5
Nordevald Software Ballot Box
Copyright 1989-91 Marianne Love, Nordevald Software
The Ballot Box Door is compatible with DCI BBS Software, V.3.xx.
The Ballot Box allows users to vote on up to 20 questions, with a
choice of 10 options on each question. Each question is composed
of:
QUESTION: The question, which may be 80 characters long.
TOPIC: The listing on The Ballot Box menu, 50 char.
long.
OPTIONS: Up to 10 options that the voter may choose, 50
characters each.
The user is presented with a menu listing the Voting Topics and
may select one to vote on, or choose the A)ll option and vote on
each question without returning to the menu.
Similarly, the user can review the results of the voting on one
or all questions. The user will not have the option of viewing
the results of a particular question until he has voted on it.
The results list the total number of votes cast, the options, and
the percentage who voted on each option.
Previous ballot returns can also be archived and viewed by the
users.
The SysOp commands are available from the main voting menu and
include Modify (question, topic, option), Add new, Delete, Clear
Tally (clear the voting results on a voting question), Compile
returns (archive), and Delete Voter.
Installation
Copy DCIVOTE.EXE to your /DOORS subdirectory and Add the entry to
your Doors Data File:
Status : Active
Filename : DCIVOTE.EXE
Name : <whatever you want>
Access Level : <minimum user security level for access>
Parm Type : DCI
Participation : <your choice>
Parm String : <leave blank>
Description : <your choice>
S)ave the door information and enter the door. You can now add
your voting questions.
B6
The Ballot Box Commands
User Commands
Enter # to Vote on/Review Returns
If the voter has not voted, entering the number of a voting
topic, will display the voting options and prompt the voter
for his selection. Entering the number of the option
registers the vote, entering a 0 allows the user to exit
without voting.
If the voter has already voted on the question, the results
will be displayed.
All
If the voter has not voted on all of the questions, the
Questions will be displayed continuously allowing the voter
to vote on each one without a menu display between each one.
If the voter has voted on all the questions, the results will
be continuously displayed.
Previous Returns
Will display The Ballot Box Archives Menu. The archives are
text files showing the results of previous voting.
SysOp Commands
Modify Submenu
Modify
Allows you to modify the Question, Topic, or any or all of
the Options. Votes are not changed.
Add new
Allows you to add a new Question with Topic and Options.
Also clears Also clears all votes on the question.
Delete
Deletes a Question, Topic, and Options.
Also clears all votes on the question.
Clear Tally
Clears all votes on the question.
B7
Compile
Compile the current voting results into a text file for
The Ballot Box Archives.
You will be prompted to enter a title and a filename. The
title will be displayed on The Ballot Box Archives Menu.
The filename is the name of the file (with the extension
.VOT) that the results are stored in.
Delete Voter
Remove a voter's name from the data file. This will not
prevent the user from voting in the future. This option
is provided to accompany the deletion of a user from the
bbs, to free up data file space and to prevent the
(unlikely) use of the record by someone using a duplicate
handle.
You may select I)ndividual Deletion to delete a particular
user. You will be prompted to enter the user's name.
Selecting A)uto Deletion will check each voter record to
make sure the user still has an account on the BBS. If
not, the voter's record will be deleted.
P)urging will remove all deleted records from the data
file.
Previous Returns SysOp Options
Modify (enter archive number)
Modify the Archive Title, Date, or Filename.
Enter <RETURN> at the prompts if you do not wish to alter
the current setting. If you wish to delete an entry, enter
an asterisk at the Title prompt. Select the P)urge option
when you have completed the deletions.
Purge
Remove deleted entries from the data file.
Maintenance
Records are referenced by system name. To prevent the file
size from growing too large, when updating all the voting
questions, delete VOTER.DAT or use the A)uto Delete option.
Periodically, particularly after deleting several users from
the bbs, run A)uto Delete.
B8
DCI Base Swap Utility
Copyright 1989-91 Marianne Love, Nordevald Software
The DCI Base Swap Door is compatible with DCI BBS Software,
V.3.xx.
DCIBSWAP allows you to rearrange the order of the message bases
on your system. It is designed to be run as a SysOp door. You
can rearrange all the message bases or just move one base. The
procedure is also abortable so you can use this to decide if you
want to move the bases before you actually do. If you decide to
save the new setup all message files will be renamed and the user
accounts will be updated so that all access and message pointers
are correct.
You can rearrange all the message bases or just move one base.
The procedure is also abortable, so you can use this to decide if
you want to move the bases before you actually do. If you decide
to save the new setup, all message files will be renamed and the
user accounts will be updated so that all access and message
pointers are correct.
Configuration
The door should be set up as a SysOp Door as no security checks
are made within the door to verify user access. To run as a
door, the following settings must be made from the door menu:
Status : Active
Filename : DCIBSWAP.EXE
Name : <your choice>
Access Level : <your choice>
Parm Type : DCI
Participation : <your choice>
Parms : %U %E
The %E parameter tells DCI to take the board down upon exit from
the door. This is necessary to rebuild one of the indexes that
DCI keeps in memory. If you are going to use the door from
remote, you must have DCI in a looping batch file.
Commands
The following commands are available from the menu:
1. Instructions
Brief help screen.
B9
2. Show Previous Base Arrangement
This displays the current message base setup on
your board. It is a variation of the DCI Base
Menu. You can also view the base descriptions and
list A)ll descriptions.
M)odify listing allows you to change the number of
consecutive undefined bases that are displayed on
the listing. The default is five.
3. Rearrange Bases
This displays the new arrangement and allows you
to swap the positions of two bases at a time. You
can also M)odify the listing as explained above.
The changes you make here are not permanent until
you select the Save option (#5).
4. Restore Previous Base Arrangement
Use this option to start over. Any changes you
made will be lost.
5. Save New Base Arrangement
Use this option only after you are certain that
the new arrangement is what you want. This will
rename the message files and alter the users'
records.
6. View Error File
This option only appears on the menu if errors
occur while saving the new arrangement. This is a
text listing of the errors, if any, that displayed
on your screen during the save procedure.
The errors are rare and only arise when there is a
conflict in file names when the program is trying
to rearrange the message files. The error listing
will tell you the current name of the file and
what it should be named to. If you have not
restored an old backup reflecting currently
deleted base data files, or tried to swap two
bases with similar names, there is little chance
of an error. However, if errors are generated,
simply rename the files manually using
DCIBSWAP.ERR as a guideline for the filenames.
V. Version
Display version information.
If you exit the door before Saving the new arrangement, all
changes will be lost.
NOTE: Always make backup copies of MSG.DCI and USER.DCI in case
of power failure during the save procedure.
B10
Errors
0 : success
250 : BOARD.DCI file not found
254 : Door program not keyed
Any other errors will be listed in DCIBSWAP.ERR with
explanations.
B11
DCI B-Day Reminder
Copyright 1990,91 Marianne Love, Nordevald Software
DCI B-Day Reminder is compatible with registered DCI versions
3.00 and above.
DCIBDAY creates a text file of users who are celebrating their
birthdays on the current date. It is displayed as part of the
permanent bulletin when users logon.
Configuration
The following settings must be made from the event menu:
Filename : DCIBDAY.EXE
Parms : /E %Z
Frequency: Daily
To use the Today in History format, add /T to the Event
Parameters.
It is best to set this event to run in the early morning hours.
In the permanent bulletin section of MAINBULL.MNU add the line:
%%DCIBDAY.TXT
If there are no users with birthdays on a particular day, the
file will be empty and nothing will be displayed.
If you would like to exclude the listing of any users in
DCIBDAY.TXT, enter their handles, 1 per line, to a file named
DCIBDAY.BAD in the Main DCI Directory.
Errors
Halt code information:
0 : success
20 : unable to create DCIBDAY.TXT - make sure there is room
in the Main DCI directory for this file.
21 : unable to open user file
250 : BOARD.DCI not found - using %Z parameter?
254 : door not keyed
B12
DCI Board Event Utility
Copyright 1989-91 Marianne Love, Nordevald Software
The DCI Board Utility is compatible with DCI BBS Software,
V.3.xx.
This utility allows you to change your board configuration as an
event. For example, if you wished to leave Sound on during the
day, but did not want to be bothered by it at night, you could
toggle the sound on in the morning and off in the evening using
this utility.
Similarly, you can restrict access to the file section during
peak times, or restrict new user registration to certain hours or
even days.
The following settings are configurable via this utility:
Maximum and Minimum Baud Rates Sound
Callback Verification SysOp Chat Page
Allow New Users Events Off
Allow Long Distance Callers Door Access
File Section Access Time Restrict
File Ratio
When used in conjunction with the flexible DCI event scheduler,
you will have a great deal of control over your board without
having to manually change any of the settings.
Configuration
The following settings must be made from the event menu:
Filename : DCIBOARD.EXE
Parms : /E %Z
The above parameters only tell the file to run, they do not tell
it what to do. Add to those parms, any of the following
parameters:
/B <see below> : change Minimum Baud Rate
/X <see below> : change Maximum Baud Rate
/V <TRUE or FALSE> : change Callback verification
/W <TRUE or FALSE> : change Long Distance Callback
/N <TRUE or FALSE> : change Allow New Users
/L <TRUE or FALSE> : change Allow Long Distance Callers
/E <FALSE> : change Events to off
/F <0-255> : change File Section Access
/D <0-255> : change Door Section Access
/T <TRUE or FALSE> : change Time Restrict
/R <0-10000> : change File Ratio
/S <TRUE or FALSE> : change Sound
B13
/C1 <TRUE or FALSE> : change Chat Page
/C2 <0-255> : change Chat Page Override
/C3 <TRUE or FALSE> : change Chat Interrupts
/O <TRUE or FALSE> : change Overtime Usage Allowed
/P <TRUE or FALSE> : change Private Base Display
Note: The /C option available in versions prior to 1.06 is no
longer valid; it is replaced by the /C1, /C2, and /C3 options.
Valid baud rate parameters: 300, 1200, 2400, 4800, 9600, 19200,
38400.
Each of the above parameters MUST be followed by the new value
and all parameters and values MUST be separated by a space.
Parameters may be stacked. For instance, if you wanted to
restrict activity to only the message bases during from 7 to
11pm, set up the first event as follows:
Filename: DCIBOARD.EXE
Parms : /E %Z /F 255 /D 255
Freq : Daily
Begin : 19:00
And set the second event:
Filename: DCIBOARD.EXE
Parms : /E %Z /F <normal value> /D <normal value>
Freq : Daily
Begin : 23:00
Note: To control the times/days that long distance callers are
allowed to register via callback several settings must be made.
To not allow long distance callers to register or gain access
during certain periods, turn Long Distance Allowed off and Long
Distance Callback off (/L FALSE /W FALSE). To allow long
distance callers to register via callback, turn both back on (/L
TRUE /W TRUE). In this way you can control when the board will
callback long distance numbers via an event, perhaps limited
callback times to late at night or on weekends. The hours you
set can be explained in REGISTER.MNU, Long Distance Not Allowed,
so that such users will know when they can register.
Similarly, registration for local users can also be limited to
specific hours or days.
Errors
Halt code information:
0 : success
21 : no parameters??
B14
22 : BOARD.DCI not found
25 : minimum baud parameter error
26 : maximum baud parameter error
27 : callback parameter error
28 : allow new users parameter error
29 : events parameter error
30 : file section access parameter error
31 : door section access parameter error
32 : time restrict parameter error
33 : ratio parameter error
34 : long distance allowed parameter error
35 : sound toggle parameter error
36 : long distance callback parameter error
37 : overtime allowed parameter error
38 : chat command incomplete (must be C1, C2, or C3)
39 : chat page parameter error
40 : chat page override parameter error
41 : chat interrupts parameter error
42 : private base display parameter error
If you have a parameter error, check to make sure:
1) the parameters are separated by spaces
2) the new value is within the ranges listed above
B15
DCI BBS Call Log Utility
Copyright 1989-91 Marianne Love, Nordevald Software
The DCI Call Log Utility is compatible with DCI BBS Software,
V.3.xx.
DCICALL can be run stand-alone, as a door, as an event, or all
three. When run stand-alone or as a door, the user will be
presented with a menu that includes listing the call log, listing
the dates and call log entries per day with a running total, and
options to remove or replace strings or entries in the call log.
When run as an event, DCICALL can be given commands to maintain a
log of call statistics, maintain the call log at a particular
size, remove strings from the call log (handy if you have
problems with a twit), and replace strings in the call log. You
can also limit the call log by the number of days' worth of
entries to maintain.
Configuration
To run as a door, the following settings must be made from the
door menu (preferably the main SysOp door section):
Status : Active
Filename : DCICALL.EXE
Name : <your choice>
Access Level : <200 or higher>
Parm Type : DCI
Participation : <not necessary>
Parms : %O %B %Z
When run as an event, the following settings must be made from
the event menu:
Filename : DCICALL.EXE
Parms : /E %O %B %Z
The above parms only tell the file to run, they do not tell it
what to do. Add to those parms, any of the following:
/L (maintain stat log)
This is the same as the List function above, except that the
information is written to CALLSTAT.LOG
B16
/T # (truncate call log)
This must be followed by the number of entries to KEEP in the
log. For instance, if you wish to maintain a call log of the
last 50 callers, enter /T 50.
/R <string> (remove string)
This will remove all entries containing the <string>. For
instance, to remove all of TWITUSER's entries, enter /R
TWITUSER.
/S <old,new> (replace string)
This will replace all occurrences of old string with new
string. For instance, to replace TMAPA with TAMPA, enter /S
TMAPA TAMPA.
/D # (maintain log by date)
This will maintain only # days' entries in the log. For
instance, if you want to keep 3 days worth of entries, enter
/D 3.
Commands
When run standalone or as a door, the user will be presented with
a menu:
1. List call log
2. List dates
3. Remove entries from call log
4. Replace string in call log
5. Version check
The first item lists all the entries in CALL.LOG.
The second item lists the dates of the entries in CALL.LOG
followed by the total of entries for that date and the total
number of entries to date. This can be used to decide how many
entries to remove from the file.
The third item allows you to selectively remove entries from
CALL.LOG. You may select to remove entries with a particular
string in them, to remove a number of entries, or to list through
the entries and select them individually. This option creates a
backup copy of the original log file, which it stores in the
/LOGS directory.
The fourth item allows you to replace a string in the log.
The Version Check displays information about this version of
DCICALL.
B17
Errors
Halt code information:
0 : success
22 : CALL.LOG not found
26 : invalid parameters
27 : invalid string replace parameter
28 : invalid remove string parameter
29 : invalid truncate parameter
30 : CALLSTAT.LOG error
250 : unable to open BOARD.DCI
254 : door not keyed
B18
DCI File Statistics Door
Copyright 1989-91 Marianne Love, Nordevald Software
The File Stats Door is compatible with DCI BBS Software, V.3.xx.
DCI File Stats provides file transfer statistics in several
different formats for both the users and the SysOp of the board.
DCIULDL.EXE can be run as a door and/or as an event. The best
use is to set it up as a door and then run an event to update the
files.
DCIULDL.EXE creates the following files:
FILESTAT.TXT Top Uploaders and Top Downloaders.
FILESTSY.TXT extended information on the Top Downloaders.
FILESTUS.TXT extended information on all users.
A user entering the door will be presented with a menu and have
the option to view the Top 20 Uploaders or Top 20 Downloaders
list or view his own file statistics.
The user's file statistics are presented to two decimal places
and calculated by both files and kilobytes uploaded and present
three ratios. Free downloads are also listed.
CoSysOps and SysOps have the additional options of viewing
extended statistics of the Top 20 Downloaders and of all users on
the system. Nine columns of information is provided, allowing
you to determine more fully the file activity on your system.
Cosysops and Sysops also have the option to view stats of a
particular user which include Files & Kilobytes Transfered,
Upload/Download Ratio, Freebie Transfers, User Ratio, Number of
Calls, Security Level, Message and System Participation, and
Available Downloads. The symbol of infinity ( ∞ ) indicates
Unlimited Downloads available.
The statistics files can be updated via the door menu by the
CoSysOp or SysOp or can be updated as an event.
Configuration
To run as a door, the following settings must be made from the
door menu:
Status : Active
Filename : DCIULDL.EXE
Name : <your choice>
Access Level : <your choice>
Parm Type : DCI
Participation : <your choice>
B19
**Parms : <none>
When run as an event, the following settings must be made from
the event menu:
Filename : DCIULDL.EXE
**Parms : /E %O %B %Z
The above parms only tell the file to run, they do not tell it
what to do. Add to those parms, either of the following:
/N : Generate New Stats (Option 7 on the menu)
It is best to include this parameter as part of a daily
or biweekly event.
/A : Generate Stats on All Users (Option 8 on the menu)
** If you wish to run the program as only a door, then the file
can be located in the DOORS directory or any directory that is in
your DOS PATH.
If you also want to run the door as an event, make sure that the
directory that DCIULDL.EXE is also in your DOS PATH.
If you would like the program to store the text files it creates
in a directory other than the DOORS directory, add the FULL
pathname of the directory to the parms string (of both the door
and event setup).
For instance, if you want the text files stored in C:\DCI\STATS\
then the parms strings would be:
Door : C:\DCI\STATS\
Event : /E %O %B %Z /<N or A> C:\DCI\STATS\
Regardless of this directory, DCIULDL.EXE must be located in the
DOS PATH.
Commands
When run as a door, the user will be presented with a menu:
1. Top 20 Uploaders
2. Top 20 Downloaders
3. Your Stats
CoSysOp/SysOp options:
4. Display Extended File Stats
5. Display All Users' File Stats
6. Display Participation Information
7. Generate New Stats
B20
8. Generate Stats on All Users
9. Generate Alternative Part Stats
Menu option 3, Your Stats, displays three lines of information:
1. Number of files uploaded, the total size of the uploaded
files, and the average size of an uploaded file.
2. Number of files downloaded, the total size of the downloaded
files, and the average size of a downloaded file.
3. The user's ratio based on files transferred and based on
kilobytes transferred.
The first option displays a list of the users who have
transferred the largest volume (measured in kilobytes) to your
board, listed in descending order. The list does not include
users with CoSysOp security levels or above. The list also may
display less than 20 users if less than 20 users have transferred
files.
The Top Downloaders provides a similar listing of those who have
downloaded the most from your system.
Both lists may be viewed by users. The Top Uploaders and Top
Downloaders lists are stored in a text file in the \DOORS
directory named FILESTAT.TXT.
Menu option 4 displays extended information on the top
downloaders. The list is stored in a text file in the \DOORS
directory named FILESTSY.TXT. (see list below)
Menu option 5 displays extended information on all users,
including CoSysOps and SysOps. The list is stored in a text file
in the \DOORS directory named FILESTUS.TXT.
Menu option 6 displays extended participation information on all
users, including CoSysOps and SysOps. The list is stored in a
text file in the \DOORS directory named FILESTUP.TXT.
Option 7 generates the files for Top Uploaders and Top
Downloaders and the Extended File Stats.
Option 8 generates the information on All Users.
Option 9 allows you to experiment with different Board
Participation Factors and Ratios and view how the various
settings would effect the users of your system. You can enter
various participation factors and a file will be created
(FILEP###.%%% where ### is the test ratio and %%% is the test
participation factor) listing all or part of the users. It is
faster if you only list 20 or so of the user records in this file
(you will be prompted for this information). You can also
specify which record number to begin with. More active users
tend to be at the beginning of the user file, while newer users
are at the end. You can then view the file. This will give you
B21
an idea how various participation factors will effect the users
rather than using trial and error.
The Extended Statistics include:
USER -- user name, truncated if longer than 20 characters
DL-K -- kilobytes downloaded
DL-F -- files downloaded
K/D -- average kilobytes per file downloaded
UL-K -- kilobytes uploaded
UL-F -- files uploaded
K/U -- average kilobytes per file uploaded
K -- ratio of kilobytes downloaded to kilobytes uploaded
F -- ratio of files downloaded to files uploaded
R -- user ratio status, Y)es or N)o
The Participation Information includes:
USER - user name, truncated if longer than 20
characters
Calls - number of times the user has called the system
(less than 7 calls increases the user's
participation rating)
Sec - user security level (also affects participation
rating)
R - user ratio status, Y)es or N)o
U:DK - ratio of kilobytes downloaded to kilobytes
uploaded (e.g., 32.0 means that 32K has been
downloaded for every 1K uploaded)
MP - messages posted bonus
RP - relative participation rating (weighted by
number of calls and security level)
TP - true participation rating (not weighted as RP
is)
Available - Number of K or files (depending on ratio
is determined) available to the user for
download with the current settings. A negative
number indicates the user has exceeded the board
ratio and would have to upload that amount to
meet the board ratio.
Following Board Ratio in the Header, (K) indicates the ratio is
by kilobytes transferred, and (#) indicates the ratio is by
number of files transferred.
Errors
Halt code information:
0 : success
21 : invalid event parameters
22 : invalid DCI directory
250 : unable to open BOARD.DCI
B22
DCI File Utility
Copyright 1990-91 Marianne Love, Nordevald Software
The DCI File Utility is compatible with DCI BBS Software, V.3.xx.
The DCI File Utility will create a text file of visible files in
all or specified directories for users to download. This file
can be optionally compressed. This option is designed to be run
as an event.
The Utility also provides two convenient options for boards with
GIF files by checking the files for information on resolution
and color. If the files have already been added to the file
section, the utility will update the file descriptions with the
resolution and color information. The utility can also be used
to add files to the data files with this additional information.
Text File of Files in Directories
Run as an event to create a text file listing of all non-private,
visible files in specified directories. The list includes file
name, size, date, and description. The file information will be
added to a specified directory so that users may download it.
The file may be zipped if desired.
Call with
/T <A,O,#> <final dir> <filename> [/Z]
<A,O,#> What directories to list:
A>ll -- open and private
O>pen -- open only
# -- the number of the directory or several
numbers separated by semicolons (e.g.,
1;3;7)
<final dir> Directory to store created file in <filename>.
What to name the created file, limited
to 8 characters, no extension.
[/Z] Optional switch to Zip the file. PKZip must be
in the DOS Path. It will be called to create the
file <filename>.ZIP using the -u switch.
Examples:
/T A 0 ALLFILES /Z
make a text file (ALLFILES.TXT) of All files, open and
private, zip the file (ALLFILES.ZIP) and store it in
directory 0.
B23
/T O 1 FILELIST /Z
make a text file (FILELIST.TXT) of all Open files, zip
the file (FILELIST.ZIP) and store it in directory 1.
/T 12 12 CADFILES /Z
make a text file (CADFILES.TXT) of all the files in
directory 12, zip the file (CADFILE.TXT) and store it
in directory 12.
/T 3;4;8 1 GIFFILES /Z
make a text file (GIFFILES.TXT) of all files in
directories 3, 4, and 8, zip the file (GIFFILE.ZIP)
and store it in directory 1.
Add GIF Files To Data Files with Resolution and Color Info
This option works similarly to the SysOp Add feature. Any *.GIF
files in the DOS directory that are not listed in the DCI data
file will be added to the data file. The description will
include information on the resolution of the GIF (eg., 320 x 200)
and the number of colors (e.g., 256 colors).
Call with
/G /A <A,#>
<A,#> What directories to search:
A>ll -- open and private
# -- the number of the directory or several
numbers separated by semicolons (e.g.,
1;3;7)
Examples:
/G /A A
search All directories for any GIF files not currently
in the data files and Add them to the data files.
/G /A 1
search directory 1 for any GIF files not currently in
the data file and Add them.
/G /A 14;15;18
search directories 14, 15, and 18 for any GIF files
not currently in the data file and Add them.
B24
Update GIF Descriptions
This option will search the specified directories for any *.GIF
files and add the resolution and color information to the file
description.
If a description already exists, the info will be added to the
second line of the description.
Call with
/G /D <A,#>
<A,#> What directories to search:
A>ll -- open and private
# -- the number of the directory or several
numbers separated by semicolons (e.g.,
1;3;7)
Examples:
/G /D A
search All directories for any GIF files and change
their Descriptions to indicate the resolution and
number of colors in the GIF file.
/G /D 1
search directory 1 for any GIF files & change their
Descriptions to indicate the resolution and number of
colors in the GIF file.
/G /D 14;15;18
search directories 14, 15, and 18 for any GIF files
and change their Descriptions to indicate the
resolution and number of colors in the GIF file.
The GIF Utilities can be run as an event though you might find it
more convenient to run them as a SysOp file door so that they are
run only when you feel it is necessary. If you have many files
in the directories or the utility will act on many files, it will
take some time. These utilities MUST be run from DCI, however.
B25
Errors
Error codes
300 - incorrect number of parameters
301 - invalid first parameter
302 - invalid second parameter
303 - invalid third parameter
304 - cannot find BOARD.DCI
305 - cannot find MAINFILE.DCI
306 - unable to add file record
307 - unable to add file record
B26
DCI MNU Swap Utility
Copyright 1990-91 Marianne Love, Nordevald Software
The DCI Menu Swap Utility is compatible with DCI BBS Software,
V.3.xx.
DCIMSWAP is a small program that will allow you to change any of
your MNU files as an event.
You can use this program to rotate Greeting, Welcome, or Logoff
screens, or any other MNU file as often as you wish. After you
create the new MNU files and configure the event, it will run
completely unattended for as long as you wish.
The MNU files can be swapped as often as you like using the DCI
event frequencies. You can swap two files or rotate up to as
many as 999.
Parameters
PARAMETERS: %Z <mnu file> <new file> <optional record file>
<mnu file>
The MNU file that you wish to SWAP with the new file. It can be
any MNU file that is located in the \MNU directory.
<new file>
The name of the file that you want to replace the MNU file with.
This is the filename ONLY, no extension.
<rec file>
Optional filename for DCIMSWAP to record next file to swap. Only
necessary if more than one MNU file is being swapped at a time.
Setting It Up
1. Create the new file, making sure the DCI dividing lines are
in the proper places . Select a filename and add the extension
'.1' to it. Put the file in the \MNU directory.
For instance, if you wished to SWAP LOGONOFF.MNU with your
special XMAS screens, first structure the new file in the same
configuration as LOGONOFF.MNU. Name the new file XMAS.1, and
copy it to the \MNU directory. In this example, LOGONOFF is the
<mnu file> parameter, and XMAS is the <new file> parameter: %Z
LOGONOFF XMAS.
If you wish to rotate several <new> files, name them successively
(i.e., XMAS.1, XMAS.2, XMAS.3, etc.). Number them in the order
in which you want them to appear. In this way, you can swap up
to 999 files. Regardless of the number of <new> files, the
B27
parameter line remains the same. The program will handle the
numbering.
2. Define the event:
Filename : DCIMSWAP.EXE
Parms : %Z <MNUFILE> <NEWFILE>
Freq : <your choice>
3. Smile, you're done.
When the program runs, it will rename the original MNU file to
<mnufile>.0 and then check to see if there is another file to
swap. If there is, the files will be swapped. If the program
finds that after swapping files 1, 2, and 3 that file 4 does not
exist, it will go back to file 1.
The program will create a small file, DCIMSWAP.DCI, in the \MNU
directory. This is how it keeps track of the next file to swap.
You can use this program to SWAP several MNU files, but each MNU
file swapping will require a separate event, and you will have to
pass an additional parameter to the program: the new name of
DCIMSWAP.DCI, so that the program does not become confused. If
you are SWAPping LOGONOFF.MNU, you might name this file
LOGMNU.DCI.
To set up two File Swaps:
Event 1 :
Filename : DCIMSWAP.EXE
Parms : %Z LOGONOFF XMAS LOGMNU.DCI
Event 2 :
Filename : DCIMSWAP.EXE
Parms : %Z MENU COLORS MENUMNU.DCI
When the first event runs, it will rotate the files you have
named XMAS.x with LOGONOFF.MNU, keeping track of the next file to
swap in LOGMNU.DCI.
When the second event runs, it will rotate the files you have
named COLORS.x with MENU.MNU, keeping track of the next file to
swap in MENUMNU.DCI.
B28
Errors
The program will return the following result codes:
0 : success
1 : invalid number of parameters
less than 3 parameters?
2 : error backing up .MNU file
check parameter 2
3 : DCIFLSW.DCI not found in \MNU directory
check parameter 4*
4 : SWITCH file(s) not found
check parameter 3
5 : Unable to rename SWAP file to MNU file
\MNU directory cluttered?
250 : Unable to open BOARD.DCI
If you get any error greater than 1, first check to make sure
that the first parameter is %Z.
* If you get tangled up trying to figure out what is causing an
error 3, first make sure that the record filename you are passing
as parameter 4 is a valid DOS filename. If it is, and the <mnu
file>.0 exists in the MNU directory, follow these steps:
1. Delete the Original <mnu file>.MNU.
2. Copy <mnu file>.0 to <mnu file>.MNU.
3. Run the event again.
B29
DCI Message Move Utility
Copyright 1990-91 Marianne Love, Nordevald Software
The DCI Message Move Utility is compatible with registered
versions of DCI 3.00 and above.
DCI Message Move Utility allows the SysOp to move more than one
message at a time from one base to another and keep message
threads intact. All the messages or a thread of messages within
a specified range may be moved.
The reply references of the moved messages will be updated as
well as the users' pointers. If a user has not read all the
messages in the base the messages are moved to, his pointers will
not be updated, but otherwise the pointers will be set to the
first unread message.
The Message Move Utility can be run as a door and as an event.
Configuration
Place the file DCIMUTIL.EXE in the main DCI directory.
To run as a door, the following settings must be made from the
SysOp Door Menu:
Status : Active
Filename : DCIMUTIL.EXE
Name : <your choice>
Access Level : <your choice>
Parm Type : DCI
Participation : 0
Parms : <none>
If there are many messages to be moved, you may consider setting
up an event to handle the chore during a period of low board
activity.
When run as an event, the following settings must be made from
the event menu:
Filename : DCIMUTIL.EXE
Parms : /E <oldbase> <newbase> <firstmsg> <lastmsg>
<A/T>
Frequency : Yearly
<oldbase> - number of base to move messages from
<newbase> - number of base to move messages to
<firstmessage> - number of first message to move
<lastmessage> - number of last message to move, 0 indicates
highest message in base
<A> - move All messages
B30
<T> - move message Thread that begins with
firstmessage
For instance, if you wanted to move a thread of messages
beginning with message number 200 from base 4 to base 15, the
parms string would be:
/E 4 15 200 0 T
Setting the event up as Once will prevent it from running again.
Door Commands
Scan Messages: Scan and read messages in the bases to decide
which messages to move. Messages can be M)arked (see Queued
Message Move below).
Move Messages: Move a range of messages from one base to
another. When prompted, specify the base to move the
messages FROM, the base to move the messages TO, and whether
or not to move ALL the messages or just the THREAD.
List Queue: List all the entries in the queue. Optionally
delete queue entries.
Queued Message Move: The Message Move Queue will hold up to 10
entries. An entry consists of the FROM and TO bases, first
and last message numbers, and whether to move all messages or
thread. M)ark first messages during the Scan to add them to
the queue. When the queue is full or you have made all your
selections, use this option to begin the mass move.
Information: Brief information on the above commands.
Version: display version information.
Errors
Halt code information:
0 : success
1 : Invalid number of parameters
Check your event parm string to make sure it includes
all of the following:
/E <oldbase> <newbase> <firstmsg> <lastmsg> <[A/T]>
2 : The event <oldbase> number is invalid.
3 : The event <newbase> number is invalid.
4 : The event <firstmessage> number is invalid.
5 : The event <lastmessage> number is invalid.
250 : Unable to open BOARD.DCI
B31
DCI Potty Door
Copyright 1990-91 Marianne Love, Nordevald Software
The DCI Potty Door is compatible with DCI BBS Software, V.3.xx.
This door is a humorous way of dealing with prompt timeouts on
the system. When a user enters the door, he is given five
minutes before the door will return him to the door menu prompt.
This allows special users to remain on line if temporarily
interrupted.
Configuration
To run as a door, the following settings must be made from the
door menu:
Status : Active
Filename : DCIPOTTY.EXE
Name : <your choice>
Access Level : <your choice>
Parm Type : DCI
Participation : <your choice>
Parms : <none>
It is suggested that you restrict access of the door based on
security level.
B32
DCI Upgrade Door
Copyright 1990-91 Marianne Love, Nordevald Software
DCI Upgrade Door is compatible with registered DCI versions 3.00
and above.
DCIUPGR.EXE is designed to be run as a door program. Based on
answering a questionnaire, reading a text file, or a setting in
the user's account, the user's access to some feature on the
board is increased.
For instance, new users may not be given the F (file menu)
command as part of their main command options. By going into the
door, selecting the entry for file access, agreeing to abide by
certain rules of file system use, the F will be added to their
main options.
The Questionnaire is flexible, allowing questions to be of any
length, and providing some formatting of user responses.
Questions can also be linked to other questions.
All answers will be stored in a text file that can be viewed from
within the door or from the DCI SYSOP: FILES menu.
Configuration
To set it up as a door in either the Main or File Door sections,
the following settings must be made:
Status : Active
Filename : DCIUPGR.EXE
Name : <your choice>
Access Level : <your choice>
Parm Type : DCI
Participation : <your choice>
Parms : %U
Once the door is set up, enter it and select SysOp Options from
the menu, then select M)odify and indicate Record number 1.
Each record in the Upgrade door has several standard fields:
Name - this may be up to 70 characters long. This is
displayed to the users on the menu.
Status - three available settings:
Active : allow users to select this option.
Inactive : do not allow users access, do not
delete.
Delete : do not allow users access, delete this
option.
B33
Filename - this is the name of the textfile containing the
text to display or the questionnaire. The
Question file will should be named <filename>.UPG.
The program will create the response file as
<filename>.RES.
Several fields can be used to determine whether or not to allow
the user access to the upgrade option. If the user fails to meet
ONE minimum requirement, he will not be allowed to continue.
Any of these minimum requirements can be disabled by setting it
to -1.
The following fields determine who has access to the option:
Minimum age - user's age must be greater than or equal to this
value.
Maximum age - user's age must be less than or equal to this
value.
Minimum security level - user's security level must be equal
to or greater than this value.
Minimum time - user's time limit must be greater than or equal
to this.
Minimum message participation - the user's message
participation (number of messages posted, the
"bonus" points) must be equal to or greater than
this value.
Minimum board participation - the user's overall RELATIVE
participation must be greater than or equal to this.
This is the user's participation compared to the
board participation.
Minimum base access - this is the number of a message base on
the board that the user must have access to.
Once you have set up the record, you must create the Upgrade
file. This is a text file containing codes that tell the door
what to do as it reads the file. This file must be formatted
very carefully. Once you have created it, test it before
allowing users to access it.
The following codes tell the program how to read the upgrade text
file:
[Q] = Question, displays the following text as a question.
For your own information, you can add a number or
note within the brackets, e.g. [Q1] and [Qaddress]
would both be acceptable.
B34
[A] = Answer, prompts for user input depending on the code
following the right bracket (]):
Y = displays "Answer [Y/N]" allowing the user to enter
either a "Y" or an "N".
M = multiple choice, displays "Enter Choice [<choices>]: "
allowing the user to input one of the choices. The
choices must follow the M code. For instance,
[A]M1234 indicates a multiple choice answer where
"1", "2", "3", and "4" are acceptable responses.
The display would be "Enter Choice [1234]: ".
S = string input, with minimum and maximum length and type
specification. The display is "A: " followed by
dots
indicating the maximum length allowed.
[A]S<min length>,<max length>,<type>
The maximum length is 70 characters; if 0 is
entered, 70 will be assumed.
The minimum length is 1 character; if 0 is entered,
5 will be assumed.
The type is indicated by one of the following codes:
# : allow input of numbers only
^ : upper case input
* : upper and lower case input
F = formatted input. The display is entirely dependent on
the codes listed after [A]F.
The following codes are used:
^ : input of . ABCDEFGHIJKLMNOPQRSTUVWXYZ only
* : input of !"#$%&''()*+,-/:;<=>?, numbers, upper and
lower case letters
# : input of "0123456789" only
Any other characters are displayed to the user. For
instance, to prompt for a telephone number, enter
[A]F(###)###-####. The program will display "(" and
wait for the user to enter 3 numbers and then
display ")" and so on.
[G] = Go To, tells the program to skip to the question indicated
by the number following the code (e.g., [G]10 = Go To
Question 10). The program counts the questions
sequentially from the beginning of the file -- it ignores
numbers that may be included with [Q] (e.g., [Q10]).
[U] = If the user entered appropriate input, upgrade the user
according to the codes that follow the [U]. The first code
must be an Input Code:
B35
0 = the user entered no input
1 = the user entered Y to a Y/N question, entered input on
a string or formatted question, or entered the first
option on a multiple choice question.
2 = the user entered N to a Y/N question or entered the
second option on a multiple choice question.
Input codes may be greater than 2 on multiple choice
questions. The input code is the position within the
choices of the character the user selects (e.g., if the
choices are "ABCD", A=1, B=2, C=3, and D=4).
The following Upgrade Codes are supported:
[S]# = increase user's security level to #; if the user's
security level is greater than #, there will be no
change.
[T]# = increase user's time limit to #; if the user's time
limit is greater than #, there will be no change.
[H]# = increase the user's handles allowed to #; if the
user's handles allowed is greater than #, there will
be no change.
[U]# = increase the user's uploaded files stat by #; note
this is added to the user's current setting.
[K]# = increase the user's uploaded K stat by #; note this
is added to the user's current setting.
[M]? = add Main Menu options to user's Main Opts. This can
be one option or several. For example, [M]* would
give the user the Main Menu option of entering the
Main Door section.
[F]? = add File Menu options to the user's File Opts. This
can be one option or several.
[B]# = give user access to base number #.
[G]# = go to question number #.
[A] = abort questionnaire, return user to menu.
[N] = do not upgrade this user.
[W] = Wait, displays "Press any key --> ".
; = Comment, text on a line beginning with a semicolon will not
be displayed. Use this option to include comments in the
UPG file.
B36
Door Commands
The Door Menu offers the following commands:
A numbered list of any questionnaires that are Active and
that the user meets the minimum access requirements.
When the user enters the number of a questionnaire, it will
be displayed to the user. The user's responses and any
upgrades will be recorded in the response file
<filename.RES>.
I)nformation - a brief explanation of the door.
S)ysop Options - appears if user has CoSysOp or SysOp level
access.
V)ersion - display version information
The SysOp Commands Menu offers the following options:
L)ist Records - an abbreviated listing of all defined
questionnaire records. Entering a record
number at the prompt will allow you to
modify the record.
M)odify Record - Enter the number of a record number to
modify it. To add a new record, enter a
number higher than the highest defined
record number.
P)urge Deleted Records - Remove all records with a status of
DELETED from the data file.
S)how Results - view a response file selected from a menu.
The Modify Record Option also includes a Test Upgrade File
procedure. This will allow you to test the .UPG file to see how
the door will interpret the codes in it. No changes will be made
to your user record during this test.
B37
The test procedure will:
- display the question number (not displayed to users)
- display the question
- prompt for an answer
- indicate the input value of the answer (not displayed to
users)
- translate upgrade codes and values, if possible (not
displayed to users)
- if an upgrade code is entered improperly, the door may not
be able to interpret the rest of the line, including
the upgrade value.
- GoTo Question Number translation is done, but will be
ignored (the questionnaire will not skip ahead to the
GoTo Question).
Several Test<#>.UPG files are included. These are examples of
different ways to create Upgrade Files. These can be viewed with
the T>est procedure (create "dummy" records using these filenames
and then mark them as Deleted and Purge the file before allowing
users access).
Errors
Halt code
0 = success
250 = error opening BOARD.DCI
254 = door has not been keyed
B38
APPENDIX C - BIRD LAKE SUPPORTING SOFTWARE
Bird Lake Software's programs for DCI are developed in full
cooperation with Nordevald Software.
BLUPurge, A DCI User Purge Utility
Copyright (c) 1990 Bird Lake Software
BLUPurge is compatible with DCI BBS Software, V.2.23 and above.
Overview
BLUPurge is an add-on utility for the DCI BBS. It allows mass
deleting of users based on selection criteria specified on the
command line. SysOps, CoSysOps, and users marked as Special will
not be deleted even if they otherwise meet the criteria.
Messages posted either to or from deleted users will also be
marked as deleted. It is possible to obtain a listing of the
users and messages that will be affected before doing any actual
deletions. BLUPurge may be run either from the DOS command line
or from DCI as an event.
Command line parameters
When run from the DOS command line the following parameters
should be used. The options, selections, and restrictions can be
placed in any order and the case of the option does not matter.
For each option the portion inside brackets is optional. For
example, /PUR and /PURGE are the same. A summary of this
information may be obtained by running BLUPurge with no options.
BLUPurge <options> <selections> <restrictions>
<options>
/I[nfo]
Report detailed version information and exit.
/DC[ipath]=<path>
Specifies the directory where BOARD.DCI can be found.
For example: /DCI=e:\dci
/PUR[ge]=ALL
/PUR[ge]=DEL
If messages have been deleted run DCIPurge. If ALL is
specified then DCIPurge will be run for all bases. If DEL is
specified then DCIPurge will be run only for bases in which
BLUPurge has deleted messages. Note: Memory constraints may
prevent DCIPurge from being run directly from BLUPurge when
BLUPurge is run as an event. In this case, DCIPurge should
C1
be run as a separate event.
/PA[gelen]=<n>
Set page length for log file. 0 = continuous. The default
is 24 lines. For example: /PA=30
<selections>
/D[ays]=<low>,<high>
Specifies the range of days since last call to select. For
example /D=30,60 will select users who have not called in
between 30 and 60 days.
/S[ecurity]=<low>,<high>
Specifies the range of security levels to select. For
example /S=60,70 will select users with a security
level between 60 and 70.
/C[alls]=<low>,<high>
Specifies the range of number of calls to select. For
example /C=1,5 will select users who have called between 1
and 5 times.
/M[essages]=<low>,<high>
Specifies the range of number of large messages posted to
select. For example /M=0,1 will select users who have posted
no more than one large message. Please note that more
messages than specified may actually be deleted as DCI only
counts messages over a certain length.
/UK=<low>,<high>
/DK=<low>,<high>
Specifies the range of upload and download kilobytes,
respectively. For example, /DK=600,900 /UK=0,0 will select
users who have downloaded between 600 and 900 K of files but
have uploaded nothing.
/UF=<low>,<high>
/DF=<low>,<high>
Specifies the range of number of uploaded and downloaded
files, respectively. For example, /UF=1,5 /DF=15,20
will select users who have uploaded between 1 and 5 files and
downloaded between 15 and 20 files.
<restrictions>
/L[ist]
Do not delete anything, only produce a listing of selected
users and messages.
/SK[ipmsgs]
Do not scan messages for posts from or to deleted users.
This can only be used if /List is also used. Use of this
option will save much time when determining which criteria
you wish to use for purging users.
C2
/LD[only]
Only select long distance callers.
(Validation status = 3 or 5).
/LO[calonly]
Only select local callers.
(Validation status = 2 or 4).
/N[ocallback]
Only select unverified users.
(Validation status = 4 or 5).
For the options which allow a range selection, either of the low
or high portion of the range may be omitted. This is the same as
selecting 0 or infinity, respectively. For example, /D=30 will
select users who have not called in 30 or more days. /S=,60 will
select users with security levels of 60 and below.
When run as an event the same command line options should be
used, however an extra parameter, %E, must be specified. This
will tell DCI to exit with a halt code of 0 after BLUPurge is
completed. Your batch file must be set up to recycle the board
when this happens. For example:
Event #10 Last result: 0
1. Event Name : Upurge 1 6. Due Date : 10-30-91
2. Filename : BLUPURGE.EXE 7. Begin Time : 18:45
3. Status : Active 8. Until Time : 21:00
4. Slide : YES 9. Frequency : Yearly
5. Parameters : Defined
%E /D=45,999 /M=0,0 /S=0,60 /PUR=ALL
Output
BLUPurge will display a running status report on the local
console so that you can tell how the program is progressing. An
output file, UPURGE.LST, is also produced. That file will
contain a list of the options in effect as well as a list of all
users and messages selected for deletion. Each run of BLUPurge
appends to this file so you may wish to purge it periodically.
Finally, a summary of the number of users and messages selected
for deletion is placed in DCI's activity log. Any error messages
occurring are also recorded there.
Running BLUPurge
BLUPurge may be run from any directory as long as the DCI path is
specified on the command line. The DCI path is not required if
BLUPurge is run from the main DCI directory. Note that if the
/PURGE option is specified then BLUPurge must be run from the DCI
directory or else DCIPurge will fail. If run as an event,
BLUPurge will be run from the DCI directory by default.
C3
Safety
Unless the /List option is specified, BLUPurge modifies the
following files: USER.DCI and *.HDR. UPURGE.LST and ACTIVITY.LOG
are always modified. Before modifying USER.DCI a backup file,
USER.BAK, is created. This file will overwrite any previous
USER.BAK in the DCI directory. This will allow you to restore
your user file in the event that a run is interrupted or if the
incorrect parameters have been specified. Please note that the
*.HDR files (message headers) are not backed up by BLUPurge. If
you want backups of these files before BLUPurge modifies them you
must back them up yourself.
Users are deleted by overwriting their name fields with <DELETED>
<USER>. Users may be undeleted by replacing their name with
their real name and rebuilding the handle and primary indexes.
Messages are not actually deleted, they are simply marked as
deleted so that DCIPurge will later delete them. Any message may
be undeleted by using the change message header feature from
DCI's SysOp menu.
BLUPurge may be aborted at any point by hitting control-C or
control-break. However, any changes which have been made will
not be undone.
Program messages
The following is a list of error messages that BLUPurge can
generate. These will be displayed to the screen and recorded in
the activity log.
- Can't <operation> <filename>: <dos error message>
An open, close, read, or write operation on <filename>
failed. The <dos error message> indicates what went wrong.
This error does not always cause BLUPurge to abort. When it
does, the result code is set to 1.
- Can't delete <filename>: <dos error message>
BLUPurge could not delete one of the user file indices.
- Could not allocate deleted users array!
The array which stores user numbers of deleted users could
not be created. If possible, increase the amount of memory
that is available to BLUPurge. Sets the result code to 1.
- DCI has not been keyed.
Run your DCI key program to key your copy of DCI. The result
code is set to 251 or 252.
C4
- DCI version 2.23 or higher is required.
BLUPurge is only compatible with DCI versions 2.23 or higher.
The result code is set to 249.
- Message scan skipped.
The /SKIPMSGS parameter was specified, so no message bases
were scanned.
- <number> message(s) selected for deletion.
Indicates how many messages were selected to be deleted.
- Must be run from a registered copy of DCI.
BLUPurge will not work with evaluation copies of DCI. The
result code is set to 253.
- No purge specifications given.
None of the command line arguments given specified what
users to delete.
- No users selected for deletion.
No users matched the deletion parameters given to BLUPurge.
- Program must be keyed.
Run your doorkey program to key BLUPurge. The result code is
set to 254.
- Result code <number>.
This message is given at the end of every run. It indicates
what result code is being returned to DOS. A successful run
will return 0.
- <number> user(s) selected for deletion.
Indicates how many users were selected by BLUPurge for
deletion.
- User interrupt.
BLUPurge detected a ctrl-C or ctrl-break from the local
keyboard. Sets the result code to 2.
C5
Support
Support for BLUPurge may be obtained in the following ways (in
order of quickness of response):
- The DCI Utility Support Base on Bird Lake BBS
(813-265-3256)
- The DOORS: DCI & Otherwise base on Nordevald Software BBS
(813-961-0788).
- On Bix through mail to wcowley
- Through US Mail to:
Wes Cowley
P.O. Box 280138
Tampa, FL 33682-0138
Feel free to direct any questions, suggestions, or bug reports to
me in one of those places.
Bird Lake Software does not currently provide telephone support.
If you encounter a problem the following things may help in
troubleshooting:
- Check DCI's activity log for any error messages or other
clues that might help pinpoint the problem.
- Double check the parameters to make certain they are
correct.
When reporting a problem, please including the following
information:
- Any relevant activity log entries.
- The UPURGE.LST file.
- Any relevant circumstances surrounding the problem.
C6
APPENDIX D - LONGBOW PUBLISHING
In cooperation with Nordevald Software, Longbow Publishing offers
users and SysOps the option of ordering the DCI BBS Software
documentation in a professionally printed and bound manual as
opposed to printing the file in its ASCII format.
The manual includes the full text of the ASCII file which is
provided with the DCI BBS Software package. The order forms for
DCI BBS Software, Nordevald Software doors and utilities, and
Bird Lake Software utilities for DCI, are in the manual along
with each program's specific documentation. The documentation
for DCI specific doors are not included with the ASCII file for
DCI. Those are normally provided with the registration of the
programs.
Please use the order form in Appendix E to order the manual.
Questions regarding orders can be directed to ARROWSMITH on the
Nordevald Software BBS (813)961-0788 or the LONGBOW BBS
(813)961-3653.
D1
APPENDIX E - REGISTRATION AND ORDER FORMS
DCI BBS Software
A license is required to use DCI BBS Software. You may obtain a
license by filling out the enclosed registration form and mailing
it with your payment to:
Nordevald Software
P.O. Box 280138
Tampa, FL 33682
Upon receipt of the registration and payment, Nordevald Software
will mail to you a registered copy of the DCI BBS software and
documentation for the software or you may download your software
package from the Nordevald Software BBS.
Personal Checks will be accepted by Nordevald Software, but the
software will not be available to the registrant until the check
has cleared. A money order or cashier's check will ensure faster
receipt of the software.
This registration form is for a single-site license only. Please
contact Nordevald Software for information on multi-site
licenses. Nordevald Software will accept requests for
customization of DCI BBS Software for multi-site use.
TERMS
Your signature on the registration form is your acceptance of the
following terms:
1. DCI BBS Software, doors, utilities, documentation, and
related materials, hereafter referred to as the Product, are
protected by copyright law. Copies may be made for
archiving purposes only. The documentation may not be
copied, distributed, or reproduced in whole or in part
without prior written consent of Nordevald Software.
Disassembly and reverse compilation of the software is
expressly forbidden.
2. Nordevald Software grants to the registrant a license to
use one copy of the Product.
3. Nordevald Software will deliver to Registrant the Product,
which contains a notation as to the registration, and
supporting documentation.
5. Registrant will be entitled to support services, via
Nordevald Software BBS, (813)961-0788, or by mail at the
following address, for the period of one year.
6. Registrant will be entitled to any minor upgrades of the
Product.
7. Registrant will be entitled to reduced costs when
registering future versions of the Product.
8. Neither the Product nor this Agreement may be assigned,
sub-licensed or otherwise transferred without the prior
written consent of the Nordevald Software.
9. Registrant will not allow copies to be made and distributed
to anyone else and will report any unauthorized acquisition
of the Product to Nordevald Software immediately.
10. Registrant understands that this Product is a single node
version. Attempts to run this version as multinode will
void this agreement.
11. Registrant will forfeit all rights and services if the
Product has been modified by unauthorized means.
LIMITATIONS OF LIABILITY
1. Nordevald Software makes no warranties with respect to the
licensed program.
2. Nordevald Software will make a reasonable effort to fix any
software-related problems that are found by Registrant which
prevent the program from performing the functions described
in the software documentation.
3. The foregoing warranties are in lieu of all other warranties
expressed or implied, including but not limited to the
implied warranties of merchantability and fitness for a
particular purpose. Nordevald Software shall not be liable
for any lost profits, or for any claim or demand against
Registrant by any other party. In no event shall Nordevald
Software be liable for consequential damages.
DCI BBS Software Registration Form
Name: ___________________________________________________________
Address: ________________________________________________________
City, State, Zip: _______________________________________________
Name of BBS: ____________________________________________________
Data Phone Number: _______________ PC Pursuit Node: ___________
Modem Type: ______________________ Min/Max Baud: ______________
System Type: _____________________
___ I have an account on Nordevald Software BBS under the name
__________________________.
___ I don't have an account on Nordevald Software BBS, please
add one for me:
Account name: ____________________________________
(maximum 30 characters)
Account password: ________________________________
(maximum 8 characters)
___ The BBS is private.
___ I grant Nordevald Software permission to publicize my BBS
name and number.
I, ________________________, understand that by signing this
registration form, I have agreed to the terms specified by
Nordevald Software in the above documentation. I understand them
fully and will abide by them.
Date: ___________ Signed By: ___________________________________
Optional info:
Where did you hear about DCI BBS Software? ______________________
Where did you download the evaluation copy? _____________________
How long have you been running the eval copy? ___________________
How long have you been a SysOp/cosysop? _________________________
What other BBS programs have you run? ___________________________
Is your BBS a general, message, file, or game board? ____________
Does your BBS have a particular theme or purpose? _______________
_________________________________________________________________
What DCI features first attracted your attention? _______________
_________________________________________________________________
Comments: _______________________________________________________
_________________________________________________________________
_________________________________________________________________
Nordevald Software Order Form
Date __________
Name ____________________________________________________________
Address _________________________________________________________
City, State, Zip ________________________________________________
Bulletin Board Name _____________________________________________
Bulletin Board Phone Number _____________________________________
DCI Version Number ______________________________________________
DCI Registration Number _________________________________________
I am ordering the following:
DCI BBS Software . . . . . . . . . . . . . ($90.00) _______
All of GROUP I & II Doors & Utilities . . ( 99.00) _______
DCI BBS Software Evaluation Copy . . . . . ( FREE) _______
GROUP I
AutoBase Access Door . . . . . . . . . . . ( 8.00) _______
Ballot Box Voting Door . . . . . . . . . . ( 8.00) _______
B-Day Reminder . . . . . . . . . . . . . . ( 8.00) _______
Base Swap Door . . . . . . . . . . . . . . ( 8.00) _______
Board Event Utility . . . . . . . . . . . ( 8.00) _______
Call Log Utility . . . . . . . . . . . . . ( 8.00) _______
File Statistics Door . . . . . . . . . . . ( 8.00) _______
File Utility . . . . . . . . . . . . . . . ( 8.00) _______
MNU Swap Utility . . . . . . . . . . . . . ( 8.00) _______
Potty Door . . . . . . . . . . . . . . . . ( 8.00) _______
Seven of GROUP I . . . . . . . . . . . . . ( 52.00) _______
Eight of GROUP I . . . . . . . . . . . . . ( 58.00) _______
Nine of GROUP I . . . . . . . . . . . . . ( 64.00) _______
Ten of GROUP I . . . . . . . . . . . . . . ( 70.00) _______
GROUP II
Message Move Utility . . . . . . . . . . . ( 15.00) _______
Upgrade Door . . . . . . . . . . . . . . . ( 15.00) _______
Bird Lake User Purge . . . . . . . . . . . ( 15.00) _______
Two of GROUP II . . . . . . . . . . . . . ( 25.00) _______
Three of GROUP II . . . . . . . . . . . . ( 35.00) _______
Shipping and Handling** . . . . . . . . . ( 5.00) _______
I have enclosed a cashier's check or money order for $ _______
** ______ I will download the software from Nordevald BBS.
______ Please mail the software to me, I've enclosed $5.00.
I prefer ___5¼" DD ___5¼" HD ___3½" DD ___3½" HD.
Mail to: All software is shipped via
Nordevald Software first-class mail. Most orders
P.O. Box 280138 are mailed or posted on the
Tampa, FL 33682 BBS the day they are received.
Longbow Publishing Order Form
Date ______________________________________________________
Name ______________________________________________________
Address ___________________________________________________
___________________________________________________
City, State, Zip __________________________________________
Are you a registered DCI Sysop? ______ Reg #_______________
If not, are you a Sysop using other software? _____________
If so, what software are you using? _______________________
What is the name of your BBS? _____________________________
What is your voice #? _____________________________________
What is your DATA #? ______________________________________
The cost of the documentation is $20.00 U.S. + $5.00 shipping.
We accept personal checks, Cashiers checks, and money orders.
Personal checks require 1 week to clear.
Make checks payable to:
Eric Neff
14511 Midland Greens Place
Tampa, FL 33265